If the original save save set still exist, you must specfy the CLONEID along with the SSID.
Besides that, what do you want to achieve?
- To redirect the data, it could be a sequence issue. Try:
recover -v -d "D:\rest" -S 4206392649/cloneid
- To recover solely the directory, use:
recover -v -S 4206392649/cloneid -a "D:\rest"
To verify how may files are inside the save set, run
mminfo -q "ssid=4206392649/cloneid" -r "client,name,savetime,level,ssid,cloneid,totalsize,nfiles"
To verfy, which files are inside the save set, load the tape and on the storage node, run the following command:
scanner -n -i -S 4206392649 device
Tape restoration from old tape (same data) has been completed. No error. Earlier we used "scanner -m -S <SSID> \\.\Tape1" (only m) on old tape and we were getting "Bad or missing record" while restoration. Later, we did "scanner -im -S <SSID> \\.\Tape1" and now, it completed tape restoration successfully. The discussion which i posted is the second retry from the different tapes.
FYI - "scanner -i -S <SSID> \\.\Tape1" is enough.
As NW knows that the file index info would not make sense without the media index info, it would recover the media db records if necessary.
BTW - if you already supply the SSID why would you scan what you already have 😉
Usually we are using “–m” option because we need to restore whole saveset , not particular files & folders. Later, we used “-im”. Thanks for your suggestions.
“skill, will and hill”