Re: [Networker] Corrupt save sets?

You could try recreating the client.

1. delete the old client;
2. rename the old client index folder to *.old;
3. create the new client and add the old client as an alias to the new client 
(even though it's the same name, the sid is different);
3. stop the networker daemons;
4. rename the index folder for the old client to the new client's name;
5. start the networker daemons.

You may see that the first backup will be a full, however, the above will allow 
you to preserve the old client's indexes if you have to go back.

I'm coming from a windows environment so I'm not sure of the syntax but the 
order of operations should suffice.

Good luck.

Carter
Ext. 5711
cfowler AT city.london.on DOT ca
 

-----Original Message-----
From: koef AT WEBBING.ORIGIN-SRV DOT COM 
Sent: Thursday, August 08, 2002 4:31 PM
To: koef AT WEBBING.ORIGIN-SRV DOT COM; NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Corrupt save sets?

Server: NetWorker 6.0.1.Build.174 on Linux
Client: NetWorker 6.0.1 on Windows 2000

Server has backupped the client for months without errors.
Recently the client's C:\ disk died. After reinstalling the OS and Networker
client, firing up Networker User and pressing the "Recover" button, after
some time the message appears,

  No index was found. You have not backed up any files from this machine.
  If you are doing a directed recover you have not backed up any files from
  the selected client, or you need to be connected to the server as the
  supervisor.

Then I tried a save set recover from the client's GUI:

  You cannot browse the save sets for the chosen client.

On the server, I can see all the savesets for this client just fine.
Guessing there was something wrong with the indexes, I used scanner -i
to recover all indexes from tape. No difference.
Then I recovered a save set for this client on the server itself:

  # scanner -v -S 707250433 /dev/nst0 > clientname.scan

Using "strings clientname.scan" I saw familiair windows 2000 filenames.
However,

  # /usr/lib/nsr/uasm -r -n -v < clientname.scan

gives no output at all. As a sanity check, I did the same test for
a different windows 2000 client in my network and it gave me the expected
list of files in the save set.
I recovered all save sets for the disaster client, and on none of them
uasm showed any files in them. It seems the save sets are somehow corrupted.
Copying clientname.scan to the windows machine and use UASM.EXE on it
gives also nothing.

Any suggestions greatly appreciated.

--
Koef.

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