Hi
We are looking to utilise our SAN infrastructure to improve the speeds of our backups as they are currently running slowly across the LAN.
Having tried to go through with the SAN SSO configuration, we discovered that the current info in the database was wiped out - Scheduled jobs/job history/media sets etc - all gone! We've now recovered back to were we were before trying out the SAN SSO config, but would still like to use it for the speed benefits.
We have 3 buildings in a triangle shape:-
Building 1 - Hosts a 2008 R2 server running BE 2010 R3 acting as the main backup server and 2x HP tape libraries
Building 2 - A 4 node Hyper-V cluster all running Server 2008 R2 also. With a HP SAN.
Building 3 - A second 4 node Hyper-V cluster also all running Server 2008 R2. With a HP SAN.
All these devices are attached to 8Gb fibre switches that are all linked in the triangle. All Hyper-V servers can see the tape libraries.
We first off tried using BEUtility.exe to create a New Media Server Group which contained the backup server and one of the Hyper-V nodes (only using one node for testing at the moment) and set the backup server as the Primary SAN SSO server. Then, with full Backup Exec installed on the Hyper-V server (only a trial for testing) we also used BEUtility to set the backup server as the Primary SAN SSO server. Could this be were it's gone wrong?
After this, we looked at creating a new job and could access the Hyper-V node and list it's drives and files etc but noticed that the tape libraries had been renamed and our backup to disk folders were gone. We cancelled the test job and investigated why the data had gone instead and recovered back to our initial config.
Were we on the right lines? The SAN SSO seems to be a tricky beast to configure? Can anyone shed any light on the best way of configuring this please? Also, should we then see any options relating to the SAN SSO when configuring a new job?
Sorry for the long post, very confused here!
Thanks for your time.
Barry-R