As we're only running two 'bots and a baby SCSI SAN (HP MSA500), I'm not
as worried about the backplane. If I had a herd of StorageTek
Timberwolves hanging off of it, I might be a little more hesitant. :>)
-dd
>>> "Williams, Kristopher L" <kris.williams AT hp DOT com> 11/4/2005 4:20:20
PM >>>
Sounds like a good plan - Here are two quick thoughts
1. It has been mentioned on this list that Linux (mostly redhat) isn't
quite ready for primetime as a master yet. I haven't played with it
yet,
so I can't comment beyond what I've read on this list.
2. I have been successful many times copying the image files from one
master two the other, both with different names. I currently do this
for
DR purposes for one of my customers. In that environment I'm using a
Windows 2000 master and NBU5.0 MP3. We replicate
%install%\veritas\netbackup\db\images\* to the remote DR center master
that has a different name. When it comes time to do a DR, everything
is
good to go with no db import needed. This won't help with the media
db's, but might save some time with the images. Again, not sure if
this
will still work for newer version of NB but worth a shot.
Like always.....TEST, TEST, and TEST some more!
Thanks,
Kris
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Dan
Dobbs
Sent: Friday, November 04, 2005 5:30 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] migration to a new server
Greetings, all.
Currently, we are running 5.1 on an HP-UX L-class box, with a couple
'bots (one old Surestore juke with (4) DLT4000s, one Neo juke with a
DLT220). It seems to work reasonably well. We have a few hundred tapes
'in circulation'. So, we're probably one of the smaller sites that
visit
this list. :>)
We're taking the plunge, and planning a migration of our backup
environment to Red Hat Linux (the HP-UX maint fees will pretty much
pay
for the change).
My thought on migration was to hook the Neo juke up to the new RH box,
install Netbackup with the new servername, and import the SDLT tapes
(around thirty). When they have been satisfactorily imported into the
new server's database, backup the catalog on the old box, and then
delete the media from the HP-UX box.
Then, we'd run the boxes simultaneously for a while, and once we feel
confident with the new server, follow the same basic operation with
the
'regular' dlt's and the other juke and decommission the HP-UX box.
It would appear that this isn't all that different than a disaster
recovery scenario, exc that I can't re-use the catalog as the server
name is different (and I've always hated the current name of the
backup
server anyway).
What other recommendations/caveats could you folks suggest? I'm sure
that I've missed a slew of things. :>)
Cheers,
-dd
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
