Re: [Veritas-bu] NBU Server Upgrade
2011-05-19 14:42:42
Here's what we do for a UNIX (Solaris)
server refresh.
-Install NBU and patch to the same level
on the new server
-Make a final catalog and system backup
of the old server
-Shut down NBU on old system
-Use tar and some other OS tricks to
do a simultaneous tar and copy to the remote machine
-Swap over library/drive connections
and configure in OS (this can be done before if a switched connection)
-Swap IPs and hostnames
-Reboot both servers, making sure NBU
does not start on boot
-Reconfigure drives/robot
-Test
-Resolve any issues
Of course this is UNIX, so, IMO, there
are some OS tools that make this so much easier than on Windows. Perhaps
cygwin could help, or there are some Windows tools you're aware of to achieve
the same goal. This has worked extremely well for several migrations, though
it can be time consuming. It has taken us most of a day before, but that
is dependent on what size pipe you have available when doing the file transfer
(100Mb not fun).
Here's another idea. What if you setup
your new server, then used DoubleTake or something like that to mirror
NBU to it? Or, what about pulling the drives (hopefully a mirror set) and
putting them in the new server? Yes, there would probably be some hardware
differences, but hopefully Windows could get past that. Then you could
upgrade Windows to 2008 and be done. Another idea is to upgrade to Win2k8
and then move to the new server via one of the above methods.
Whatever you end up doing, I recommend
a practice run if you can afford that. Don't do anything to your old system
that would prevent falling back.
Rusty Major, MCSE, BCFP, VCS ▪
Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge
Suite 200, Houston TX 77079 ▪ 281-584-4693
Keeping People and Information Connected®
▪ http://availability.sungard.com/
P
Think before you print
CONFIDENTIALITY: This e-mail (including
any attachments) may contain confidential, proprietary and privileged information,
and unauthorized disclosure or use is prohibited. If you received
this e-mail in error, please notify the sender and delete this e-mail from
your system.
"McDonald, James F.
II" <JAMES.F.MCDONALD.II AT saic DOT com>
Sent by: <veritas-bu-bounces AT mailman.eng.auburn DOT edu>
05/19/2011 09:43 AM
|
To
| <veritas-bu AT mailman.eng.auburn DOT edu>
|
cc
|
|
Subject
| [Veritas-bu] NBU Server Upgrade |
|
My current NBU server has lost its warranty
coverage and instead of paying for more coverage, I was given a new server
that has a warranty intact. I need to upgrade to this newer server
so I just wanted to get some guidance on the procedure to do so. The
current setup is a Dell 2950, running Server 2003 and NBU 7.0. There
is tape storage attached to the current NBU server, via a SCSI card. The
new setup will be in a newer Dell 2950, running Server 2008 and
NBU 7.0. I will need to transfer everything (db’s, images, tape
storage, etc.) to the new server. Below are some instructions I found
online. Please comment, add or take away. This will be a first-time
“recovery” for me, so any guidance would be greatly appreciated.
Recovery When Windows is Intact
Master Server Disk Recovery for
Windows
Before starting, verify that
you have:
NetBackup server software for Windows
The latest NetBackup catalog backup
on tape or disk
Determine the install_path in which
NetBackup is installed.
By default, NetBackup is installed
in C:\Program Files\VERITAS
.
Recovering the Master Server
(Windows intact)
To recover the Master server
with the operating system intact
1. Partition the disks as
they were before the failure.
2. Install NetBackup server
software. However, do not configure any NetBackup policies or devices.
3. Install any NetBackup
patches that had previously been installed.
4. Update the external mapping
files.
5. Enable debug logging
by creating the following directories:
install_path\NetBackup\logs\tar
install_path\NetBackup\logs\bpinetd
6. Start the NetBackup Client
service and stop all other NetBackup services. Use the NetBackup
Activity Monitor, or the Services application in the Windows Control Panel.
7. Use the bprecover command
to recover the NetBackup catalogs: Choose one of the procedures under “Recovering
the NetBackup Catalogs for Windows”
on page 544.
8. When catalog recovery
is complete, start the NetBackup services that are not already running.
Use the Activity Monitor, or the Services application in the Windows
Control Panel.
Master Server Disk Recovery
for Windows
Caution: In
step
9, do not restore
files to the install_path \NetBackup\db, install_path \NetBackup\var ,
or install_path \Volmgr\database directories. These directories were recovered
instep
7 and
overwriting them with regular backups will leave the catalogs in an inconsistent
state.
9. Restore all other files:
a. Start the NetBackup Administration
interface on the master server.
b. Start the Backup, Archive,
and Restore utility.
c. Browse for restores and
select the partitions that were lost.
d. Deselect the install_path
\NetBackup\db, install_path\NetBackup\var
and install_path\Volmgr\database directories (see the caution above).
e. Start the restore.
10. When all partitions
are restored, check the debug logs in the directories created instep
5. If there are any ERR
or WRN messages, resolve the problems before proceeding.
11. Reboot the system. This
replaces any files that were busy during the restore. When the boot process
is complete, the system is restored to the state it was in at the time
of the last backup
James McDonald
System Administrator
SAIC - IISBU
410-312-2232
_______________________________________________
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
|
|
|