Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can I restore files from a different media server? 2
- Thread starter EnochChum
- Start date
-
2
- #3
How to restore files from a media server other than that used to perform the backup
Details:
Under normal operation, restores will always be directed to the media server that performed the backup. There are times when this behavior is not desirable. Some examples of when to use this method:
Two (or more) servers are sharing a robot, with each host either directly connected to some of the drives, or connected to the drives in a shared storage option (SSO) environment. A restore is requested while one of the servers is either temporarily unavailable or is busy doing backups.
The backup window is very limited and any time spent performing restores would prevent critical backups from taking place. So, a dedicated restore Media Server is defined that does not perform any critical backups.
A media server has been removed from the NetBackup configuration, and is no longer accessible.
This TechNote describes a process that causes restores of backups made by one media server to be performed on a different media server. This process will cause all restores of backups performed by Media Server A to be performed by Media Server B instead. This method requires administrator intervention.
Note: The media server override applies to all storage units on the overridden media server. This means restores for any storage unit on the "fromhost" will go to the "tohost."
The process requires modification of the bp.conf file on UNIX media servers and registry edits on Windows NT media servers.
To override the NetBackup media server for a restore:
1. If necessary, physically move the media and update the Media Manager volume database, using the Media Manager administrative utilities
2. Modify the NetBackup configuration on the master server:
If the master server is a UNIX NetBackup server, perform the following steps:
As root user, add the following entry to the /usr/openv/netbackup/bp.conf file:
FORCE_RESTORE_MEDIA_SERVER = fromhost tohost
where fromhost is the media server that performed the original backup and tohost is the desired media host to use for the restore.
If the master server is a Windows NT NetBackup server, then perform these steps instead:
Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. Great care should be taken when making changes
to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Use the RegEdit application to modify the key HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
to add the value FORCE_RESTORE_MEDIA_SERVER and then set the newly added value to fromhost tohost, where fromhost is the media server that performed the original backup and tohost is the desired media host to use for the restore.
3. Force the NetBackup request daemon (bprd) on the master server to re-read its configuration by either using the appropriate File menu item on the main NetBackup administrative utility or by stopping and restarting bprd.
To revert back to the original configuration for future restores, simply delete the changes made in Step 2 above.
Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and that is truth.
Details:
Under normal operation, restores will always be directed to the media server that performed the backup. There are times when this behavior is not desirable. Some examples of when to use this method:
Two (or more) servers are sharing a robot, with each host either directly connected to some of the drives, or connected to the drives in a shared storage option (SSO) environment. A restore is requested while one of the servers is either temporarily unavailable or is busy doing backups.
The backup window is very limited and any time spent performing restores would prevent critical backups from taking place. So, a dedicated restore Media Server is defined that does not perform any critical backups.
A media server has been removed from the NetBackup configuration, and is no longer accessible.
This TechNote describes a process that causes restores of backups made by one media server to be performed on a different media server. This process will cause all restores of backups performed by Media Server A to be performed by Media Server B instead. This method requires administrator intervention.
Note: The media server override applies to all storage units on the overridden media server. This means restores for any storage unit on the "fromhost" will go to the "tohost."
The process requires modification of the bp.conf file on UNIX media servers and registry edits on Windows NT media servers.
To override the NetBackup media server for a restore:
1. If necessary, physically move the media and update the Media Manager volume database, using the Media Manager administrative utilities
2. Modify the NetBackup configuration on the master server:
If the master server is a UNIX NetBackup server, perform the following steps:
As root user, add the following entry to the /usr/openv/netbackup/bp.conf file:
FORCE_RESTORE_MEDIA_SERVER = fromhost tohost
where fromhost is the media server that performed the original backup and tohost is the desired media host to use for the restore.
If the master server is a Windows NT NetBackup server, then perform these steps instead:
Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. Great care should be taken when making changes
to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Use the RegEdit application to modify the key HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
to add the value FORCE_RESTORE_MEDIA_SERVER and then set the newly added value to fromhost tohost, where fromhost is the media server that performed the original backup and tohost is the desired media host to use for the restore.
3. Force the NetBackup request daemon (bprd) on the master server to re-read its configuration by either using the appropriate File menu item on the main NetBackup administrative utility or by stopping and restarting bprd.
To revert back to the original configuration for future restores, simply delete the changes made in Step 2 above.
Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and that is truth.
I use this script to change what media server is used for a restore. You will need to enter the old media server and the new one, along with the dates that the backup was taken. Let me know if it helps:
#!/usr/bin/ksh
PATH=$PATH:/usr/bin:/usr/local/bin:/usr/openv/netbackup/bin/admincmd
export PATH
#set -x
DATE=`date '+%m%d%Y'`
echo "please enter the new server"
read NSERVER
echo "please enter teh old server"
read OSERVER
echo "please enter the policy"
read POLICY
echo "date format is mm/dd/yyyy example 06/16/2003"
print -n "Please enter the backup SDATE \t "
read SDATE
print -n "Please enter the backup EDATE \t "
read EDATE
if [[ -x /tmp/chirssy ]]
then
rm /tmp/chirssy
fi
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY -U
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY |awk '{print $1}' > /tmp/chirssy
for i in `cat /tmp/chirssy`
do
/usr/openv/netbackup/bin/admincmd/bpmedia -movedb -ev $i -newserver $NSERVER -oldserver $OSERVER
done
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY -U
for i in `cat /tmp/chirssy`
do
vmquery -m $i | grep robot | grep slot > /dev/null
if [[ $? -eq 1 ]]
then
echo "WARNING: TAPE NUMBER $i IS NOT IN THE LIBARARY"
else
echo "$i is in the libary"
fi
done
#!/usr/bin/ksh
PATH=$PATH:/usr/bin:/usr/local/bin:/usr/openv/netbackup/bin/admincmd
export PATH
#set -x
DATE=`date '+%m%d%Y'`
echo "please enter the new server"
read NSERVER
echo "please enter teh old server"
read OSERVER
echo "please enter the policy"
read POLICY
echo "date format is mm/dd/yyyy example 06/16/2003"
print -n "Please enter the backup SDATE \t "
read SDATE
print -n "Please enter the backup EDATE \t "
read EDATE
if [[ -x /tmp/chirssy ]]
then
rm /tmp/chirssy
fi
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY -U
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY |awk '{print $1}' > /tmp/chirssy
for i in `cat /tmp/chirssy`
do
/usr/openv/netbackup/bin/admincmd/bpmedia -movedb -ev $i -newserver $NSERVER -oldserver $OSERVER
done
/usr/openv/netbackup/bin/admincmd/bpimagelist -media -d $SDATE -e $EDATE -policy $POLICY -U
for i in `cat /tmp/chirssy`
do
vmquery -m $i | grep robot | grep slot > /dev/null
if [[ $? -eq 1 ]]
then
echo "WARNING: TAPE NUMBER $i IS NOT IN THE LIBARARY"
else
echo "$i is in the libary"
fi
done
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question