Yes, I agree with the bug comment. In my environment I can go ahead and make restores come from the backup server that did the backup. However, if I did want
to load balance the restore among different media server, I would still get failures for Enterprise Client machines since they are not licensed to restore anything but themselves! I’m hoping that before I need this functionality Symantec will have this hole
plugged!
Thanks!
Scott Chapman
Senior Technical Specialist
Storage and Database Administration
ICBC - Victoria
Ph: 250.414.7650 Cell: 250.213.9295
From: Marianne Van Den Berg [mailto:mvdberg AT stortech.co DOT za]
Sent: Monday, May 30, 2011 1:21 PM
To: Chapman, Scott; 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: Re: Restore Problems
Same experience - searched high and low... This behaviour is totally against everything I knew about NBU restores.
Logged a call with Symantec after finding the 1st TN. I included a BCS engineer on a response who happened to be doing a NBU assurance at the same customer. He mentioned the TN that fixed it.....
I still feel that what is happening is a bug.
Please share the TN with your case engineer - they DON'T know everything (nobody does)!!
Regards
M.
Sent from my BlackBerry Bold
From: Chapman, Scott
To: Marianne Van Den Berg; 'VERITAS-BU AT mailman.eng.auburn DOT edu'
Sent: Mon May 30 22:06:37 2011
Subject: RE: Restore Problems
Wow, well done Marianne! That did the trick for us.
My next question is why didn’t Symantec give me this answer when I opened a case?
Thanks so much Marianne!
Scott Chapman
Senior Technical Specialist
Storage and Database Administration
ICBC - Victoria
Ph: 250.414.7650 Cell: 250.213.9295
From: Marianne Van Den Berg [mailto:mvdberg AT stortech.co DOT za]
Sent: Monday, May 30, 2011 12:31 PM
To: Chapman, Scott; 'VERITAS-BU AT mailman.eng.auburn DOT edu'
Subject: RE: Restore Problems
Hi Scott
Problem is described in this TN :
http://www.symantec.com/docs/TECH87200
DataDomain restore is sent to ‘Any’ media server instead of media server that performed the backup.
Solution:
http://www.symantec.com/docs/HOWTO44563
Create the touch file USE_BACKUP_MEDIA_SERVER_FOR_RESTORE, as follows:
On UNIX and Linux master server, create the file in /usr/openv/netbackup/db/config
USE_BACKUP_MEDIA_SERVER_FOR_RESTORE is a global setting and always forces restore to the server that did the backup.
Regards
Marianne
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Chapman, Scott
Sent: 30 May 2011 06:06 PM
To: 'VERITAS-BU AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Restore Problems
Hello everyone, I’m wondering if anyone else out there is having the same problems that I’m having…
Master Server: NBU 7.0.1, Solaris10
Enterprise Client: NBU 7.0.1, RedHat 5.?
OST Device: DataDomain 880
So all of our backups go through our master server, whether tape or OST. My issue arrises when we do a restore from the DD, NetBackup can pick the Enterprise Client to do
the restore… To begin with the Enterprise client is obviously not defined in any of the clients server lists, secondly, even if it was, it should fail the restore because it is only licensed to backup/restore itself!
My understanding is this is a problem with the restore gui, because a restore from the CLI can define the media server to service the restore request.
Is anyone else seeing this issue? If so, have you been able to work around it (besides making server admins do restores from the CLI)?
Scott Chapman
Senior Technical Specialist
Storage and Database Administration
ICBC - Victoria
Ph: 250.414.7650 Cell: 250.213.9295
This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized
copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately.
This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying,
dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately.