Hi,
I appreciate that you figured out the way. But i would
request you to post the results or solution for the problems u
mentioned in ur mail. That will help others people too.
Thanks,
Ashish
On 3/22/06, George Sinclair <George.Sinclair AT noaa DOT gov> wrote:
> Never mind. I figured it out. Duh!
>
>
> George Sinclair wrote:
>
> > Thanks! Yes, this is exactly what we want to do. Our backups only run
> > at night so I don't mind having to bring up the old server before I
> > leave to go home and shut down new sever before continuing tests next
> > day. I have some questions on this that I'm unclear about:
> >
> > 1. How to create file device on the old server. Will I have to
> > re-partition the disk to create such a device?
> > I do have a few external disks, but these have already been
> > partitioned and are in use, but there is plenty of space on them.
> >
> > 2. How is the bootstrap directed to this device? Does it get saved as
> > a file that I can just copy over, or will it be an entire directory
> > structure requiring me to tar it first?
> >
> > 3. How will mmrecov on the new server know where to find it? Don't see
> > an option for telling mmrecov not to use a local tape device. Man page
> > just says 'mmrecover -q -v'?
> >
> > 4. I assume I won't have to recover the client indexes, delete the old
> > server client or add new server client since new server will have same
> > host name?
> >
> > 5. Is there any reason I could not just tar /nsr/mm as is?
> >
> > Thanks.
> >
> > George
> >
> > Stuart Whitby wrote:
> >
> >> Your *best* choice for doing this would be to use the bootstrap
> >> backup, which allows you to bring your recovered media DB up without
> >> holes (best way I've found to change platform, btw). You can do this
> >> by creating a file device, directing the bootstrap backup to it, then
> >> taking that directory across to the other system and running mmrecov
> >> there.
> >> Doing this using the same hostname will be pretty simple. Clients
> >> already know which server to talk to, and this is pretty much a
> >> no-brainer change, or can be done as a test DR scenario. Shut down
> >> your original server while you do this and ensure that your new
> >> server uses its IP address rather than simply shutting down NetWorker
> >> on it (or down its NICs). The other server will still be available
> >> on the network otherwise, and you'll have IP conflicts etc.
> >> If you only do backups at night, switching over like this isn't a
> >> problem. Running them through the day requires you to keep your new
> >> server in "test" in relative isolation until you can be sure that you
> >> can transfer operations in as seamless a manner as possible.
> >> Cheers,
> >>
> >> Stuart.
> >>
> >> -----Original Message-----
> >> From: Legato NetWorker discussion on behalf of George Sinclair
> >> Sent: Mon 20-Mar-06 15:34
> >> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >> Subject: [Networker] Copying the bootstrap or equivalent?
> >>
> >> Hi,
> >>
> >> Looking to install NetWorker 7.x on a new Solaris box and wanted to
> >> keep same hostname as old Solaris server (6.1.1) to avoid any
> >> problems with media database, etc. Wanted to test out new server but
> >> keep old server in place until testing can be completed. Is is
> >> possible to use 'uasm' to make a copy of the bootstrap, or the
> >> equivalent of the media database, on current server and then recover
> >> to replacement (new) server, assuming both servers are running the
> >> same flavor of Unix, in this case Solaris?
> >>
> >> On old server (runs 6.1.1 on Solaris 2.8)
> >> -----------------------------------------
> >> uasm -s /nsr/mm > somefile
> >> copy somefile to new server
> >> Stop NetWorker
> >>
> >> On new server (Solaris 2.9)
> >> ----------------------------
> >> Modify /etc/hosts so new server has alias same as old server host
> >> name (/etc/nsswitch.conf is set to look in files first).
> >> Install Networker 7.x
> >> Stop NetWorker
> >> Rename /nsr/res and whatever else first
> >> uasm -r < somefile
> >> Start NetWorker
> >>
> >> Not sure if I would need to delete the old server client and recreate
> >> since I want it to have the same name. Some time ago, Legato
> >> recommended maintaining the same host name for consistency when
> >> moving to a new server? If this would work, should I shut down the
> >> old server before running the 'uasm' command even if I know nothing
> >> is running? I'm trying to avoid having to move the tape library on
> >> the current server over to the new server to run mmrecov.
> >>
> >> Thanks,
> >>
> >> George
> >>
> >>
> >> 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
> >> wit 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
> >> wit 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
> > wit 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
> wit 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
>
--
Thanks,
__________________________________
Ashish
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
wit 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
|
