Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Suspect Savesets 1

Status
Not open for further replies.

minzbigr

Technical User
Mar 24, 2006
10
US
Hello,

I have Networker Server 7.3.2 Jumbo 11 running on Windows 2003 SP2. Client in question is an AIX client running 7.3.2 Jumbo 11 client.

All of a sudden (since around June 1st or so), this client has started throwing suspect savesets. I have had EMC on the phone multiple times, but they have gotten nowhere. Daemon log shows nothing.

Obviously the suspect savesets can't be cloned. The kicker is that once the volume has a suspect saveset, it puts that volume to Read Only, thus preventing the full use of that volume.

Any ideas, questions help????????

Thanks!
 
suspect" means that NW can not read (part of) the media. In this case it will flag the save set to "suspect" so that NW will then recover from the clone media.

The error can be due to a media or a hardware error and can not easily be determined. You may change the save set status using "nsrmm -o notsuspect -S ssid" and try to recover (from another drive).

Good luck.
 
Ok that definitely worked thanks! What if I wanted to do a mass search for all suspect savesets and change them all? Also is there a way to take a bunch of backups that got spread across a bunch of tapes and consolidate them on one or two tapes (without cloning)? Basically moving the original saveset.....

Thanks so much for your help.
 
You may create a script using mminfo to search for suspect save sets and add a nsrmm command to change the status.

Then what you can to is use "nsrstage -S ssid/cloneid -b destination_pool" to move these save sets to another piece of media.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top