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!

problem with save set recover, HELP!!

Status
Not open for further replies.

rdcwedq

Technical User
Nov 27, 2002
5
SE
while I was trying to use the save set recover feature to recover a backed-up file that has passed the period of it's browse policy.

Error messages comes in Save Set Recover Status window as below.
recover: write failed to ./home/rdcgun/bck/2002-04-13/Brev3.pgd.R : Bad file number

recover: recover failed: Error receiving files from NSR server 'ecnshsr204'

Please help!! Thanks a lot
 
Is the current version on the client the same as when the file was originally backed up?

Use mminfo to determine whether the saveset is valid and complete: mminfo -avV -q 'ssid=<ssid>'
 
Thanks a lot!! I try mminfo
I think it's ok from the return of mminfo command. I pasted part of below. What can I do next, please advise.

volume client date time size level name
save time ssid first last file rec volid total fl
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 77 MB full /export/home
1031400223 87949 0 78582951 65 500 8290 2048031184 hr
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 138 MB full /export/home
1031400223 87949 78582952 220205743 66 0 8290 2048031184 mr
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 82 MB full /export/home
1031400223 87949 220205744 304206947 67 0 8290 2048031184 mr
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 87 MB full /export/home
1031400223 87949 304206948 393397695 68 0 8290 2048031184 mr
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 60 MB full /export/home
1031400223 87949 393397696 455042603 69 0 8290 2048031184 mr
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 58 MB full /export/home
1031400223 87949 455042604 514354503 70 0 8290 2048031184 mr
 
Your mminfo output shows flags hr and mr. the &quot;r&quot; means that it is not in the client index, but can be recovered.

It's the &quot;t&quot; and &quot;m&quot; that worries me. Not that they exists. What is missing is a saveset entry that has a &quot;t&quot; flag. The h=head, m=middle, and t=tail. i.e. your output shows a head and the middle saveset, but the tail section is missing, and therefore the saveset is incomplete.

If the backup server has the same type of file system as the client, then try recovering the data to the server, either with a directed saveset recovery, or by using a scanner/uasm command. See man scanner for example on how to do this.
 
got this line at the end of mminfo command reture.
ECNSHSR202.790 ecnshsr207 09/07/02 20:03:43 23 MB full /export/home
1031400223 87949 2024452368 2048031183 91 1 8290 2048031184 tr

Does this mean something?
 
Like I said, try recovering the data to the server, either with a directed saveset recovery, or by using a scanner/uasm command.

See man scanner for example on how to do this.
 
Hi Wallace88,

the lost data restored. thanks a lot for your help
 
got this line at the end of mminfo command reture

volume client date time size ssid fl lvl name
000023L1 dimsum 01/27/04 04:29:18 PM 603 MB 371068161 cr incr /mis

what should i do to recover 1 file under this save set? Thanks.
 
If you know the EXACT pathname you can do the following:

recover -S ssid -a pathname

According to the manual pages, this is called an "automatic" recovery.
 
I tried it before, but matching 0 files.

Is there any other way?.....to change the status (recovery) of save set to browse.
 
No - it must work! - The only alternative is to rebuild the file index for that save set.

Unfortunately, the command line does not forgive - for instance on UNIX it will also look at lower/upeer cases.
 
matching 0 files could simply mean that the path you specified is not in the saveset.

Try the following to get a complete list of what files are in the saveset:

recover -S ssid -a -n

Once you verified the path and file name, then try the recover with the correct path/file
 
yes, try the saveset recover form commad line in this case after locating the SSID and if that fails try scaning the tape with scanner -i. In my exp do not specify more parameters for scanner its a tempramental command that works fine if less parameters are specified.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top