I have seen that silly thing with 2GB... I think that some sort of bug as it should not happen since version 6.x where ssid cut off size was abandoned. Check what build you have.
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.
That would be me. In our environment we're trying to use AES in an all UNIX environment. We I try to do restores, they'll sometimes fail with 'no decryption key available!'.
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.
ble1
4 Operator
•
14.4K Posts
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