07-11-2011 05:30 AM
Environment:
We have a Clustered Master server + 2 media servers in Location A - our DR location
We have 5 media servers + the passive node of our Cluster in Location B
We have just brought online a 3rd location, location C
Problem:
I backing up servers in Location C using media servers in Location C When they come to try and duplicate to location A I sometimes get the above error. I think the product is trying to load balance between the servers, it is always trying to use media servers in location B unfortunately there is no route between location's B and C and there won't be.
Is there any way to only allow it to use the media servers in its geographical location? I have turned on the alternate read server, but that appears to make no difference.
Many Thanks
Matt
07-11-2011 06:35 AM
Please share information about your duplication job? Tape duplication or OST? SLP or manual duplication?
The 'load balancing' problem is a 'known issue' with OST duplications and restores. It is described in this TN http://www.symantec.com/docs/TECH87200 and is solved by creating the USE_BACKUP_MEDIA_SERVER_FOR_RESTORE touch-file as explained in TN http://www.symantec.com/docs/HOWTO44563
(FORCE_RESTORE... and FAILOVER_RESTORE.. is normally NOT an option where multiple media servers are used - it's chasing a 'moving target'!)
07-11-2011 06:36 AM
What storage medium, tape, disk, or OST device?
07-11-2011 07:18 AM
SLP's and it's Data Domain.
Thanks
07-11-2011 07:22 AM
refer to Marianne's posts, that should do it :)
07-11-2011 07:38 AM
Is that the General Server >> Media Host Override setting?
So I set that to be itself?
original backup server |
restore server |
servera | servera |
serverb | serverb |
That what you mean?
Ta
Matt
07-11-2011 08:03 AM
As per my post, we have found that creating the empty touch-file USE_BACKUP_MEDIA_SERVER_FOR_RESTORE as explained in TN http://www.symantec.com/docs/HOWTO44563
was better than relying on FORCE_RESTORE... and FAILOVER_RESTORE.. (or Media Host Override) entries.
Well that was our experience at a large customer with multiple media servers at each site.
We have only implemented the 'touch-file' which solved the problem.
Your example seems good. It should work as per this section in the TN:
"To ensure that the same media server is used to make the backup and the restore, specify the same name for the backup and restore server."
09-07-2011 07:30 AM
Any update Matt?