Install the LTO3 tape drive to the OLD server while still using old
server name. backup critical data to tape, read in tape after you have
created the new server. I have received requests to restore data that
was 20 years old. Had to recreate a server including outdated software
to allow us to restore.
*** NOTE: I would call EMC prior to this and go through the required
steps to ensure you do this correctly.
Best of luck.
Semper fidelis, /ALE
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Michael Leone
Sent: Tuesday, September 07, 2010 10:30 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Advice needed on replacing server with new hardware
*and* renaming, at the same time
I have a stand-alone server running NW 7.4.5; it has an SDLT-320 tape
library. We will be replacing it with a new server this weekend, that
has
a LTO-3 library. At the same time, we will be changing the name of the
server (to conform with current server naming standards). Just to add a
bit more aggravation to the mix, the SDLT-320 tape library won't work on
the new server (there are no free SCSI connectors, and we have no PCI-E
cards to use in the new server, and won't be buying any).
SO: here's what I'm hoping I can do.
--- Can you make a NW server backup of info to disk? I mean the mm
database, etc. All the stuff needed to do a mmrecov ?
- Fri night, make a final full backup to tape, of all server data and NW
info.
- Rename the old server to it's new name, following the procedure in
PowerLink
- Do another full backup of NW server info, to a disk drive somewhere.
-Power down the old server
-Rename the new server to the new server name (OS and DNS).
-Do a NW disaster recovery (i.e., mmrecov) from the backup made to the
disk device
-Deal with licensing re-hosting, etc.
If that works, at that point, I will have my new server, with it's new
name, and all it's old history. I want the old history, so I can browse
for restores, as needed. When I actually have to DO the restores, I can
do
them here on my NW server (which has a client with the old server name
and
client ID), and I can do the restore across the LAN.
It's convoluted, but that will work. I think. The only thing I can think
of is to just hook up the new server as a client of the old server, and
restore all the user files that way. Save as much of the history as a
CSV
file from mminfo. Shut down the old server, install NW server onto the
new
server. Whenever I need a restore, I would have to look up what tape I
need in the spreadsheet I would create from the CSV file; do the
recovery
here as mentioned earlier, and copy across the LAN.
(I'm actually already doing the CSV-as-spreadsheet tape listing already,
for an old NW server we used to have here. Yes, I still have to scan the
tapes I find listed in the spreadsheet, then do a restore, but I have
had
that lashup work ...)
I'm open to any ideas to make this more sane. :-) Hopefully easier.
Thoughts?
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
