Is it normal for the "nsrck -L7" operation to take ~5 minutes to restore
a single clients 30M index (happening to me now)?  I've got 10G of
indexes which means it will take way too long...

Thanks

Paul Trepanier


Faidherbe, Thierry wrote:

Matthew,

If you lost index and media db, it's because :
1) the media database has been restored under /var/nsr/mm. Move it back
to
/nsr/mm or to any other location being sure it's accessible from /nsr/mm

2) you should run "nsrck -l 7" to recover indexes from last tape.

HTH,

Thierry


Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

Storage & Server Integration Practice
Tru64 Unix and Legato EBS Consultant

                            HEWLETT - PACKARD
                            Compaq Computers, a member of the new HP
*********       *********   1 Rue de l'aeronef/Luchtschipstraat
*******    h      *******   1140 Bruxelles/Brussel/Brussels
******    h        ******
*****    hhhh  pppp *****   Hewlett-Packard Belgium
*****   h  h  p  p  *****   100/102 Blv de la Woluwe/Woluwedal
*****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
******      p      ******   BELGIUM
*******    p      *******
*********       *********   Phone :    +32 (0)2  / 729.85.42
                            Mobile :   +32 (0)498/  94.60.85 ***
CHANGED ***
                            Fax :      +32 (0)2  / 729.88.30
    I  N  V  E  N  T        Email :    thierry.faidherbe AT hp DOT com
                            Internet : http://www.hp.com/

________________________________________________________________________
_____

MOBISTAR SA/NV

SYSTEM Team Charleroi, Mermoz 2 Phone : +32 (0)2  / 745.75.81
Avenue Jean Mermoz, 32          Fax :   +32 (0)2  / 745.89.56
6041 GOSSELIES                  Email : tfhaidhe AT mail.mobistar DOT be
BELGIUM                         Web :   http://www.mobistar.be/
________________________________________________________________________
_____



-----Original Message-----
From: Matthew Bourne [mailto:mbourne2001 AT LYCOS.CO DOT UK]
Sent: Friday, August 23, 2002 5:11 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Moving NetWorker from SUN to HP


Hi JR,

What a coincidence !!

We have just migrated our NetWorker system from a Solaris server to an
HPUX
server.

We had all sorts of fun & games with our tech support company before
they
finally managed to get a definitive statement from Legato which said
that
this operation was not supported.  Great.

The tech support guys, however, came up with the following:

Procedure

* On your current server, create a test group and into it allocate all
clients.
* From the command line using a new tape if possible, create a final
bootstrap backup, with the syntax : savegrp -O [test group name] (O=
capital o not Zero)
* Make a note of the bootstrap ssid.  If you are unsure of this, from
the command line run : mminfo -B and make a note of the newly created
bootstrap ssid, file and record number.
* Shutdown the NetWorker services on this machine.
* On your new HP server install Legato Networker to exactly the same
path as is on the Solaris server, ensure a single drive is available

for

use.  This must be the same as on the Solaris server.
* Start the services on the HP server.
* Place the final bootstrap backup manually into the device created.
* From the command line run, and answer the questions with the
appropriate responses : mmrecov
* Once completed, stop the NetWorker services.
* In the /nsr directory, move the res directory to res.old, index to
index.old and mm to mm.old.
* In the /nsr directory move the res.R to res.
* Please note on bringing up NetWorker you will have no volumes
registered in your media database or savesets in your index's tab.
* Delete the Jukebox that is currently on your system, as this will be
using the SCSI address from your Solaris server.
* Recreate the jukebox using : jbconfig
* Can you please print / save to file all of your registration
information and send this through to me so that I can get you some new
authorisation codes for your new server.

From here you will need to run a test backup's of your clients to

ensure

that the clients can see your new server.

From this point on your new server will contain all backup's from this

point onwards.  If you need to recover historic data you will have to
disable the HP server and then bring up the Solaris server and run any
recoveries from here.

The most important point in all this is the paths *MUST* be the same.

If your /nsr directory is a symlink to filesystem /flibble on the
Solaris
box, you will need to create a filesystem /flibble on your HP box and
re-
create the links.  MMINFO really is that fussy.

This procedure effectively migrates your resources file - i.e. all your
clients, schedules, etc.

IT DOES NOT MIGRATE THE MEDIA DBASE OR CLIENT INDEXES !!

Good luck.

M.

--
Note: To sign off this list, send a "signoff" 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" 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" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=