I'm doing a little research, and the bprecover command doesn't SEEM to do what 
I need.  

Our master server is not being touched, and it's what holds the catalog, so a 
bprecover shouldn't not be needed, Right?

All the backup data lives on a SAN mount, so we should just have to move those 
volumes over to the new host (which is trivial), and the various backups should 
be presented back the way it was.

What I'm concerned with, is making sure that the install of NetBackup is 
successful, and configured right (pointing to the right master server, has the 
right tape drivers for it's vaulting process, the right robot config, robot 
control host, etc.

I've thought of this procedure:

Hostname; backupmedia2.

1) Install windows 2k3 on new server, patch, etc.
2) while unconnected to the network, install NetBackup as mediaserver, on the 
new server pointed to the correct master server.
3) Connect new server to SAN.  Do zoning magic to allow connections to the disk 
and connections to tapes/robot
4) Unconfigure tape robot paths through old media server
5) run bpdown on old server
6) connect new server to network as temp IP

RISKY STEP
7) Manually copy all data from old server ?:/program files/veritas to new server

8) remove old server from network and SAN
9) move new server to the original IP
10) connect all SAN volumes, mount them in the right places, etc.
11) bpup on new server
12) reconfigure tape robot through the new paths

I don't trust step 7 there.  I don't know what demons lurk in the registry or 
in the windows directory.

--Jason

+----------------------------------------------------------------------
|This was sent by japrice AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu