EMC got me back up and running. I sent them my mm and res folders; they
did the rename step on their test equipment; sent them back to me. With a
bit more muddling around, we got it to work. So I have my history, and am
good to go.
--
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>
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
12/01/2010 04:51:46 PM:
> From: jee <jee AT ERESMAS DOT NET>
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Date: 12/01/2010 04:54 PM
> Subject: Re: [Networker] Problems renaming server during an upgrade
> Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
>
> Michael,
>
> have you tried the following?
>
> -1) Use the old w2k3 server's bootstrap to do a DR on w2k8
> -2) Rename the NW w2k8 server to the final name (not using NMC)
> -3) Install NMC
>
> For instance:
>
> 1)
> - de-install NW from the w2k8 server
> - rename the w2k8 host from the current "B" to the old w2k3 host name
"A"
> - edit the etc\hosts file accordingly (using IP["A"] and "A" (or
> FQDN["A"] whichever name applies)
> - reboot OS
> - install NW
> - make sure NMC is not started (or not installed at all at this stage)
> - configure one drive (use jbconfig)
> - Perform a normal DR (using mmrecovr and latest "A"'s good bootstrap)
> - stop NW and replace res with the recovered res.R
> - reboot
> - carry on with the DR until completion (follow the NW DR guide)
> - reboot
>
> 2) Follow the rename procedure to rename from "A" to "B"
>
> 3) install NMC
>
> It should work...
>
> jee
>
>
>
> On Monday 29 November 2010 15:58:26 Michael Leone wrote:
> > I've opened a case with EMC, but I'm pretty sure I know what they will
> > tell me. Just wanted to see what the list thought.
> >
> > Networker 7.5.2, OS = Win2003 R2 32bit.
> >
> > On Sat my co-worker tried to rename this Networker server, as part of
a
> > process of renaming the server to a new name, take a backup, then
> > upgrading the OS to Win2008 R2. He was trying to follow the document
ID:
> > esg67624. However, he said after saving the clientid of the server,
and
> > renaming to the intermediate name in Windows, he was unable to start
the
> > NMC, to complete the renaming process. Since he was short of time, he
had
> > to continue his process of wiping out Win2003 R2 32bit and installing
> > Win2008 R2 64bit. He did install Networker onto the (now) Win2008 R2
> > server 64bit.
> >
> > So what I have is a bootstrap backup (savegrp -O -l full) of the
server
> > with the OLD name (since he was never able to finish the renaming and
make
> > a new bootstrap backup with the new name). And the server now has a
new
> > name and OS, and no media history. Is there any way I restore the
media
> > history? Note: the server does have a DNS alias of the old name.
> >
> > What I'm thinking is that I can make a client with the same clientid
as
> > previously, and (when necessary) be able to do a "nsrck -L7
> > old-client-name", since the indexes are saved on tape. Then I should
be
> > able to do recovers from the old server (semi) easily. Ideally, what I
> > want is the whole media history, but I think I'm outta luck to get
that
> > (since the server name, OS and architecture have changed, since the
last
> > backup). No "mmrecov" for me ...
> >
> > Thoughts? Comments? Abuse and denigration? :-)
>
>
>
> 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
|