Networker

Re: [Networker] Cloning issue possibly database related

2004-05-04 02:58:42
Subject: Re: [Networker] Cloning issue possibly database related
From: Michael Persson <Michael.Persson AT PROACT DOT SE>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 4 May 2004 08:57:10 +0200
Hi

I think the second error is because one of the savesets in a saveset series
is suspect or incomplete. The 3rd I'm not sure about maybe it's because
there was no valid savesets to clone!?

Check the saveset with mminfo:

mminfo -av -r ssid,cloneid,pssid,sumflags,ssflags -q"ssid=3831326977"

Check the value pssid for reference to another part of a saveset series, is
either zero for the first or if there is only one saveset in the series.
Otherwise it contains the previous ssid. If it is the first simply list all
savesets for the specific client and time period to identify if it is a
series of savesets.

You can use sumflags or ssflags to determine the status of the saveset.

Regards
Michael P

-----Original Message-----
From: Paul Crossman [mailto:pcrossma AT ORANGE DOT US]
Sent: den 3 maj 2004 22:56
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Cloning issue possibly database related


This one has got me stumped.  I'm not sure what's going on.

Here's the deal.

Networker 6.2 running on a win2k server.

I use a home grown clone script for backup cloning and it has worked
flawlessly until now.

I'm trying to clone savesets between December 1, 2003 and January 7, 2004.

I had 3 clone volumes with some data on them of savesets from the above
mentioned period.  I removed the volumes (specifying "remove file and media
index entries".  Now when I run the clone script to clone data from
12/01/2003-01/07/2004, I get failures.  I can successfully clone other data
though.  For example I ran a clone job to clone all savesets in a certain
pool in the past 12 weeks that only have one copy in the database where the
tape is in the jukebox.

Mminfo finds the savesets just fine, but when nsrclone runs I get the
following error.

C:\PROGRA~1\nsr\scripts\tmp>c:\Progra~1\nsr\bin\nsrclone -S -f
c:\Progra~1\nsr\scripts\tmp\tofulldiffclone2.txt -b "FullDiff Clone"
nsrclone: skipping aborted save set 3984803331
nsrclone: cannot clone save set 3831326977, series is corrupt
nsrclone: add_to_snodes: FALSE from vallist_add_ssid

The first nsrclone error speaks for itself, it's the 2nd and 3rd that are a
little confusing.  The Legato Knowledge Base suggests it's a staging issue,
but I'm not using staging of any kind.

Any thoughts on this???

Paul C.

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