I am using Legato 6.1 on W2K, backing up both NT and Novell clients. I am trying to do a restore from June month end which is past the browse and retention periods. The backup started at 9:00 pm on 6/30 and finished at 2:00 am on 7/01. I run scanner -i and the files are put back in the database. Everything looks ok, but I get an error (below). If I just rebuild the media index and try to run nsrck -L7 for 6/30, I can't rebuild the index with that date - it only works if I use 7/01. But when I try to do a directed recover, I get an error "No entries backed up to server xxx on 6/30/02". I think the problem is the date discrepancy between when the media thinks the backup occurred and when the index thinks the backup occurred. Is the media database corrupt?
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
File Restore
- Thread starter bpurnell
- Start date
Sounds line you ran nsrck -L7 -t "6/30"... which would default the year to 2002. Running nsrck -L7 -t "6/30/01" will work only if your client file index for that client goes that far back.
Is the media database corrupt? Not necessarily. Since you scanned in the tape, you should run the following to see what data was on that tape for the client in question. Pay attention to the flags to make sure that the saveset was completed and valid:
mminfo -avV -ot -q "volume=<volume_name>,client=<client_name>" -r "ssid,savetime,sscreate,totalsize,fragflags,name"
It may be better and perhaps faster to perform a saveset recover. Even in a saveset recover, you can specify a subdirectory or file to recover from. You can do this with the user GUI, or using command line:
recover -s <server_name> -S <ssid> -d <destination path> <Path/file to recover>
Is the media database corrupt? Not necessarily. Since you scanned in the tape, you should run the following to see what data was on that tape for the client in question. Pay attention to the flags to make sure that the saveset was completed and valid:
mminfo -avV -ot -q "volume=<volume_name>,client=<client_name>" -r "ssid,savetime,sscreate,totalsize,fragflags,name"
It may be better and perhaps faster to perform a saveset recover. Even in a saveset recover, you can specify a subdirectory or file to recover from. You can do this with the user GUI, or using command line:
recover -s <server_name> -S <ssid> -d <destination path> <Path/file to recover>
- Thread starter
- #3
Thanks for the reply - the 01 was a reference to the day - if I try to rebuild the index to 6/30/02 (the date of the backup) it wants me to use the tape that had 5/31/02's files - if I use nsrck -L7 -t "07/01/02" it will rebuild the index using the tape from 6/30/02. I can read each saveset (all 10 of them) and I'm sure it would let me restore if I could synch up the index and files. I'm thinking I've got some index corruption.
Run nsrck -L6 <client_name> to try and resolve the index issue.
Performing a saveset recovery is independant of the client index. If you know the save set id, using mminfo, then use saveset recovery, especially if you know what the name of the directory or file you want to recover.
Performing a saveset recovery is independant of the client index. If you know the save set id, using mminfo, then use saveset recovery, especially if you know what the name of the directory or file you want to recover.
- Status
Similar threads
