Networker

Re: [Networker] Moving NW server to new hardware

2004-08-03 09:12:47
Subject: Re: [Networker] Moving NW server to new hardware
From: Robert Maiello <robert.maiello AT PFIZER DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 3 Aug 2004 09:12:58 -0400
Riann,

Are you going to try one of the Unix to Windows hacks posted on the list
or an mmrecov?  :)   Yes,  please let us know how it went.

Robert Maiello
Pioneer Data Systems

On Tue, 3 Aug 2004 08:13:42 +0200, Riaan Louwrens
<riaanl AT SOURCECONSULTING.CO DOT ZA> wrote:

>To those that are interested ...
>
>I am in process of moving a server from Unix to Windows on new hardware to
>(obviously) different installation locations ....
>
>To those that are interested I will post a short summary when (if) I am
>finished and some of the snags I have (already) run into ...
>
>Regards,
>
>Riaan
>
>-----Original Message-----
>From: Chad Smykay [mailto:csmykay AT RACKSPACE DOT COM]
>Sent: Tuesday, August 03, 2004 12:36 AM
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: Re: [Networker] Moving NW server to new hardware
>
>
>We recently did a NetWorker server migration from Linux --> Linux.
>Essentially same hardware but we put our indexes on our EMC gear.  We had
>about 110GB of /nsr/index.  We started and rsync a couple days before we
>were going to do our maintenance on our NetWorker server.  Then when it
came
>time for maintenance we stopped all NetWorker services and did one last
>rsync, verified all settings on the new server (hostname, IP, etc..) and
>started NetWorker back up.
>
>We have also done similar moves with just using SCP to copy all files and
>folders from one server to another over the network, it helps if you have a
>GigE network though.
>
>One note when you do moves like these.  MAKE SURE YOU CHECK YOUR SCSIDEV ID
>FOR YOUR TAPE LIBRARIES IN YOUR NSRJB.RES FILE.  When you move to another
>server like this this ID's tend to change.  Simple edit your nsrjb.res file
>manually look for the old ID replace with new and the start up NetWorker.
>
>Hope this info helps for anyone out there.
>
>
>Chad Smykay, RHCE, LCNA
>Systems Storage Administrator
>Rackspace Managed Hosting (TM) - The Managed Hosting Specialist (TM)
>
>-----Original Message-----
>From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT 
>EDU] On
>Behalf Of Darren Dunham
>Sent: Monday, August 02, 2004 11:46 AM
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: Re: [Networker] Moving NW server to new hardware
>
>>
>> Teresa,
>>
>> If you move between equal machines
>> Say solaris -> solaris
>> or windows -> windows
>>
>> the repfered copy method is using uasm as it knows about indexes
>>
>> normal tar is not recommended and a normal networker backup will not
>> backup those files properly
>>
>> looking at your path names I assume you du have some kind of unix
>> machine
>>
>> so some kind of uasm | rsh uasm
>>
>> see also man uasm
>>
>> <<<
>>
>> Maarten
>
>As long as Networker is down, and as long as I'm going to the same machine
>(solaris -> solaris), I've never had any problems using normal utilities
>(ufsdump, tar, etc).
>
>I've often done this for copying the indexes/databases to a separate
machine
>for restores without doing a mmrecov.
>
>The only issue with using OS tools should be the same as any other running
>database.  You can't tell when the data is cached and when it's on disk.
As
>long as the application (Networker) is shut down, everything should be
fine.
>
>--
>Darren Dunham                                           ddunham AT taos DOT com
>Senior Technical Consultant         TAOS            http://www.taos.com/
>Got some Dr Pepper?                           San Francisco, CA bay area
>         < This line left intentionally blank to confuse you. >
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
to
>listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can also view
>and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.729 / Virus Database: 484 - Release Date: 7/27/04
>
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.729 / Virus Database: 484 - Release Date: 7/27/04
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=