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!

2 questions new users with Legato savegroup message and index 1

Status
Not open for further replies.

rovac2000

Technical User
Aug 13, 2002
2
CA
1

Ok I got 7 clients 4 Unix and 3 W2k the legatoserver is on Unix.
The problems is that I got a savegroup message :
savegroup alert : daily completed 7 clients (name of 1 server failed)

If I go on the volumes everything look fine Can you help me to solve this problem and why I got these message.

2 the other question is If my unix server go down How can I restore a backup without a index.



thank you
 
with savegroups, if you havent changed notifications etc, your savegroup logs can be viewed either via the nwadmin GUI, where it will show you success and failure windows, so you can ascertain what client/storage node failed to backup. from there you can run tests from the client with the save command (using verbosity levels "-vv" etc) to find the actual problem.....

Or usually on the nsr server mail will also be sent to the root account for the savegroup completion, also showing the problems....

If you want to send this backup completion info out to logfiles for each individual client in the savegroup, in the client windows in detail mode you will see an option called &quot;Owner Notification&quot;, in here you could put something like &quot;/sbin/cat - >> /usr/local/logs/<client>.log&quot;
, or just for the whole savegroup to also log into a file, do this under \custimize\notifications for the savegroup.


If you arent running any vdump/ufsdumps of your root filesystem and /usr etc for easy and faster rebuilding of your system, if you lose your system and need to boot of the cdrom and recovery everthing, you would have to reinstall networker onto this system, and using your bootstrap logs work out the SSID of the latest bootstrap and use the mmrecov command. and then nsrck -L7 to rebuild your client indexes.....or the slower way, if you know your tapes with the bootstrap and backup information, you could just scanner the tape back and or restore at the same time restore at the same time....
rebulld index/media
# scanner -iv <tape drive>
tape/with index build and recovery all data on tape
# scanner -iv <tape deive> -x uasm -rv
restore without index build
# scanner <tape drive> -x uasm -rv
restore just root filesystem
# scanner <tape drive> -x uasm -rv /

There are numerous ways to do things, but the best thing to do is ensure you have your bootstrap info somewhere other than on the system to make recovies easier....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top