The key cannot be reversed engineered by Quest (either Support or Development Departments); there are no back door mechanisms. It's up to the customer to securely maintain the passwords, otherwise they will not be able to retrieve their data
Design
WORKAROUND:
In Query Analyzer
use master
go
Xp_restore_checkpassword
This workaround may not a huge help but it does allow the user to try a bunch of passwords without attempting to restore the db each time.
xp_restore_checkpassword
@filename='pathtofilehere',
@encryptionkey='passwordhere'.
When the correct password is supplied, the message 'Encryption key matched successfully' is returned.
