06-01-2009 02:18 AM
06-01-2009 04:01 AM
06-01-2009 04:21 AM
06-01-2009 04:28 AM
Anyone have success on this. If so let me know, i have a DR test this AUG 09
Thanks for confirming this karthikeyan
06-01-2009 04:35 AM
06-01-2009 07:08 AM
All those comments are right - master server name should remain the same for catalog recovery - well, in 6.x that is really true.
However, if you "have to" do it, then Symantec consulting (on paid service, of course) can do it for you - they have the tool to convert catalog database from one master server name to another.
It was not really a DR, but I had them migrate catalog from one production master to another - 6.5, from Solaris to Linux, different hostname, same DNS domain suffix, different IP, different tape library, different install location (old = /opt/openv linked to /usr/openv, new = /usr/openv without link)
If you do not want to recover 100%, only to a certain degree, then there's a way - it's not supported by Symantec, and you do it on your own risk.
1. Take hot catalog backpu from production master
2. Bring all the tapes (catalog backup tape and and other tapes containing backup images) to DR server
3. On DR master, update robot inventory, move all of them to safe volume pool (so that they do not get over-written by newly-running backups)
4. Run phase 1 import and phase 2 import on catalog backup tape
5. Go to Backup-Archive-Restore GUI, select policy type as Hot-Catalog-Backup, and restore
/usr/openv/netbackup/db
/usr/openv/netbackup/bp.conf
/usr/openv/netbackup/var
6. And make changes to some configuration, i.e. bp.conf SERVER entries
If you do this, at least you can initiate restore for the other NetBackup clients, but I have not tested running backups - backups may or may not work.
So if your DR is for the "recovery" purpose for the NetBackup client(s) then this will suffice - but if you really want to recover your functional NetBakcup master server in the DR environment, this is not good - call Symantec consulting.
:-)
Abe
06-02-2009 02:43 AM
06-02-2009 06:01 PM
06-03-2009 12:03 AM
Version here is 6.5.2. Will try and update the post.
Raghuraam
06-03-2009 12:15 AM
07-01-2009 05:32 AM
I do not really know netbackup and some of the people we engage to do this are telling me different things.
Would like to clarify the point on hostname being the same.
Does it mean on both Master and the DR server, when you issue "hostname", both prod and dr server must show the same name ?
How would the DNS be defined then ?
Or is this only at /etc/hosts and seen locally on the server only ?
eg
Master Server A - in /etc/hosts
10.20.30.192 prod_svr_a
192.168.30.192 prod_svr_nbu
DR Server B - in /etc/hosts
10.60.30.192 dr_svr_b
192.268.30.192 prod_svr_nbu
The backup is on backup LAN 192.x segments, but on master server if you issue "hostname" is will show prod_svr_a;
while on the DR, the hostname command will return dr_svr_b
Can the backup config at the master be defined to use prod_svr_nbu ?
Will this work ?
Thanks
07-01-2009 11:06 AM