Unsolved
This post is more than 5 years old
2 Posts
0
827
June 19th, 2007 06:00
Command line restores in Networker 7.3.2 (Windows)...
Networker version: 7.3.2
Backup Client OS: Windows 2000 Advanced Server (cluster environment using EMC Celerra for storage)
Backup Server OS: Windows 2003 Standard
Backup hardware: HP MSL6000 Library with Ultrium3 media connected to EMC Celerra using HP E1200 Network Storage routers via fiber connections.
Am attempting to recover a PW2 encrypted save set using the command line interface. Am positive I am using the correct encryption password that I initially encrypted the backups with (password works fine using Networker User GUI restores).
In this instance, cannot completely browse the file structure using Networker User on the client (although after scanning the tape back into the DB, the save sets show as Browseable). When I attempt a SAVE SET recover using Networker User GUI, I get an error "winworkr: cannot recover continued ssid 935013488'. The only way I can get at the save set is via the command line RECOVER command.
Another thing (although this may be totally unrelated), when backups run, the save sets are saved in 2 GB sections (each with a separate SSID), not one big save set.
Even though I use the -p switch in the RECOVER command, the files are restored, but the file CONTENTS are still encrypted. Is there another switch or setting I can try to decrypt these files? Once again, am positive I am using the correct password. The tape will automatically load into the correct remote device (rd= ****) and read, but cannot decrypt the file contents (the filenames and directories are readable).
Thanks!
Message was edited by:
Robbie Langley
Message was edited by:
Robbie Langley
Backup Client OS: Windows 2000 Advanced Server (cluster environment using EMC Celerra for storage)
Backup Server OS: Windows 2003 Standard
Backup hardware: HP MSL6000 Library with Ultrium3 media connected to EMC Celerra using HP E1200 Network Storage routers via fiber connections.
Am attempting to recover a PW2 encrypted save set using the command line interface. Am positive I am using the correct encryption password that I initially encrypted the backups with (password works fine using Networker User GUI restores).
In this instance, cannot completely browse the file structure using Networker User on the client (although after scanning the tape back into the DB, the save sets show as Browseable). When I attempt a SAVE SET recover using Networker User GUI, I get an error "winworkr: cannot recover continued ssid 935013488'. The only way I can get at the save set is via the command line RECOVER command.
Another thing (although this may be totally unrelated), when backups run, the save sets are saved in 2 GB sections (each with a separate SSID), not one big save set.
Even though I use the -p switch in the RECOVER command, the files are restored, but the file CONTENTS are still encrypted. Is there another switch or setting I can try to decrypt these files? Once again, am positive I am using the correct password. The tape will automatically load into the correct remote device (rd= ****) and read, but cannot decrypt the file contents (the filenames and directories are readable).
Thanks!
Message was edited by:
Robbie Langley
Message was edited by:
Robbie Langley
0 events found
No Events found!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
June 19th, 2007 06:00
As for restore, you will need to check each ssid and pssid and their status.
I don't use AES as I do not see much sense, but what you have described seems as pass phrase was wrong, but if you are sure this is the pass phrase... I remember at least one person here reported issues with AES so I would suggest to open this with support.
vsemaska
194 Posts
0
June 19th, 2007 07:00
After a lot of testing and working with telephone support they said: 'We tried to investigate this issue and found that this happens with certain files on a very rare occasion'. Their solution is: 'Please use option -p pass_phrase with recover command and nwrecover when recovering encrypted files.'
So it seems NetWorker sometimes has problems passing the pass phrase from the server to the client, at least within UNIX systems.
Vic