If you have a media server, then the CATALOG BACKUP should include the
MEDIA SERVER. I have used bprecover to recover ONLY a single Media
Server.
BPRECOVER can be used for recovery of the Master And / OR Media Server.
Also, installing NBU off Network may not work, as I believe it will need
to communicate with the Master Server.
Check how your Catalog Backups are configured. If its done correctly,
you should have entries in there for the Media Server you are attempting
to upgrade.
Simon
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
zapman449
Sent: Thursday, August 07, 2008 7:15 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] How to upgrade hardware on Windows Media server?
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
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
