Backup Central

Hi,



We're planning to move our NW server to new hardware later this week.
While looking through the documentation on Legato's web site, I found
technical bulletin #121 which gives a step by step procedure for this.
The bulletin, however, says that the process is for versions 5.5.x and
earlier while we're running v 7.1.1. Has anyone done the move with
newer versions of the software? What process did you use? What
problems did you run into?



Thanks.

Teresa


Note: To sign off this list, send a "signoff networker" command via email

I found more information in the archives, but it looks like everyone
talks about using the bootstrap and recovering the indices. Can we just
copy over /nsr? Or /nsr/index?

Thanks.
Teresa



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Teresa Biehler
Sent: Monday, August 02, 2004 9:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: [Networker] Moving NW server to new hardware

Hi,



We're planning to move our NW server to new hardware later this week.
While looking through the documentation on Legato's web site, I found
technical bulletin #121 which gives a step by step procedure for this.
The bulletin, however, says that the process is for versions 5.5.x and
earlier while we're running v 7.1.1. Has anyone done the move with
newer versions of the software? What process did you use? What
problems did you run into?



Thanks.

Teresa


Note: To sign off this list, send a "signoff networker" command via
email
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

Note: To sign off this list, send a "signoff networker" command via email
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D

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



On Monday 02 August 2004 17:13, Teresa Biehler wrote:
I found more information in the archives, but it looks like everyone
talks about using the bootstrap and recovering the indices. Can we just
copy over /nsr? Or /nsr/index?

Thanks.
Teresa



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Teresa Biehler
Sent: Monday, August 02, 2004 9:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: [Networker] Moving NW server to new hardware

Hi,



We're planning to move our NW server to new hardware later this week.
While looking through the documentation on Legato's web site, I found
technical bulletin #121 which gives a step by step procedure for this.
The bulletin, however, says that the process is for versions 5.5.x and
earlier while we're running v 7.1.1. Has anyone done the move with
newer versions of the software? What process did you use? What
problems did you run into?



Thanks.

Teresa


--
Note: To sign off this list, send a "signoff networker" command via
email

--
Note: To sign off this list, send a "signoff networker" command via email

Maarten Boot,
Compuware Europe B.V.
Hoogoorddreef 5
1101 BA Amsterdam

Note: To sign off this list, send a "signoff networker" command via email

I am getting ready to do a similar procedure (solaris to solaris) and
this is the command I'm looking at using to copy over the indices.

# /usr/lib/nsr/uasm -s -i . | (cd <mounted directory on new server> ;
/usr/lib/nsr/uasm -rv)

(The . just meaning that I'm in the current index directory on the old
server.)

I've done a test run with this command and it seems to copy every thing
over nicely. I'm still looking into the other steps taht are needed to
complete the entire process.

Maarten Boot (CWEU-USERS/CWNL) wrote:
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



On Monday 02 August 2004 17:13, Teresa Biehler wrote:

I found more information in the archives, but it looks like everyone
talks about using the bootstrap and recovering the indices. Can we just
copy over /nsr? Or /nsr/index?

Thanks.
Teresa



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Teresa Biehler
Sent: Monday, August 02, 2004 9:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: [Networker] Moving NW server to new hardware

Hi,



We're planning to move our NW server to new hardware later this week.
While looking through the documentation on Legato's web site, I found
technical bulletin #121 which gives a step by step procedure for this.
The bulletin, however, says that the process is for versions 5.5.x and
earlier while we're running v 7.1.1. Has anyone done the move with
newer versions of the software? What process did you use? What
problems did you run into?



Thanks.

Teresa


--
Note: To sign off this list, send a "signoff networker" command via
email

--
Note: To sign off this list, send a "signoff networker" command via email


--
Maarten Boot,
Compuware Europe B.V.
Hoogoorddreef 5
1101 BA Amsterdam

--
Note: To sign off this list, send a "signoff networker" command via email

Note: To sign off this list, send a "signoff networker" command via email

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.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

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.EDU] On
Behalf Of Darren Dunham
Sent: Monday, August 02, 2004 11:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.edu or visit the list's Web site at
and post messages to the list.

Note: To sign off this list, send a "signoff networker" command via email

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.COM]
Sent: Tuesday, August 03, 2004 12:36 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.EDU] On
Behalf Of Darren Dunham
Sent: Monday, August 02, 2004 11:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.edu or visit the list's Web site at
and post messages to the list.

Note: To sign off this list, send a "signoff networker" command via email

---
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

On Mon, 2 Aug 2004 12:12:09 -0400, Mary-Charles Nassif
<nassif < at > MED.UNC.EDU> wrote:

I am getting ready to do a similar procedure (solaris to solaris) and
this is the command I'm looking at using to copy over the indices.

# /usr/lib/nsr/uasm -s -i . | (cd <mounted directory on new server> ;
/usr/lib/nsr/uasm -rv)

(The . just meaning that I'm in the current index directory on the old
server.)

Just a note of caution, either make sure the <mounted directory on new
server> exists and you don't make a typo or put a test in that checks your
cd has got you where you want - if the cd fails you will be in the
original directory and overwrite the original files, on unix this means
that files larger than the disk block size will be corrupted ( I know I've
done it!!!! ).



I've done a test run with this command and it seems to copy every thing
over nicely. I'm still looking into the other steps taht are needed to
complete the entire process.


Note: To sign off this list, send a "signoff networker" command via email

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.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.COM]
Sent: Tuesday, August 03, 2004 12:36 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.EDU] On
Behalf Of Darren Dunham
Sent: Monday, August 02, 2004 11:46 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.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.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.edu or visit the list's Web site at
and post messages to the list.

--
Note: To sign off this list, send a "signoff networker" command via email

---
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

Note: To sign off this list, send a "signoff networker" command via email