Troubleshooting database encryption key errors

Troubleshooting database encryption key errors

Article: 100015136
Last Published: 2018-05-17
Ratings: 2 3
Product(s): Backup Exec

Problem

You receive a message that indicates an issue with the database encryption key. The message may state that the database encryption key is incorrect, corrupt, or missing. Or the message may state that the database encryption key operation failed. 

 

Error Message

Database encryption key errors can occur when you start Backup Exec, when an operation fails, or when the database encryption key operation fails, specifically.

The following errors may occur when you start Backup Exec:

  • The import failed. The database encryption key is incorrect, corrupt, or missing.

    This message may state that the import or recovery failed because Backup Exec could not find the file, did not know the path to which it was exported, or because the key was never exported.

  • The imported database encryption key is incorrect or corrupt.

The following error may occur when a routine Backup Exec operation, such as a backup job, fails:

The database encryption key is incorrect, corrupt, or missing. Ensure that a valid database encryption key with the name "abcd.dek" is in use and retry the operation.

The following error may occur if the database encryption key operation fails:

The database encryption key operation failed.

Cause

If the message states that the database encryption key is incorrect, corrupt, or missing:

The message can occur when logging in to Backup Exec, it can appear in the event log, or it can appear as an alert after a failed job.

This message can occur in the following scenarios:

  • You recovered the Backup Exec server from a disaster, either manually or using Simplified Disaster Recovery. During the recovery process, you did not provide a database encryption key or the wrong key was provided.
  • You moved the Backup Exec server to a new computer but you did not provide the database encryption key at the new location yet.
  • The database encryption key has been accidentally deleted or corrupted while Backup Exec is running.

If the message states that the database encryption key operation failed:

If you receive a message that states that the database encryption key operation failed, Backup Exec has experienced an unknown issue with the database encryption key.

This message can occur when a user does not have the proper permissions to access the directory in which the database encryption key resides. It can also mean that the Backup Exec Database has been corrupted.

Solution

Consult the following tables to determine a solution for the message that you received.

If you receive the message when you start Backup Exec:

Message Reason Action
The import failed. The database encryption key is incorrect, corrupt, or missing. Backup Exec is unable to recover the database encryption key "abcd.dek". Could not find file "c:\key\abcd.dek". If you receive this message, you let Backup Exec remember the path when you exported the database encryption key. However, Backup Exec cannot find the key at the path.

The message should indicate a possible reason for the failure. Resolve the issue, if possible, and then click Retry to let Backup Exec reattempt to recover the key.

If Backup Exec still cannot find the key, you can manually import the database encryption key:
  1. Click Import.
  2. Browse to the directory that contains the database encryption key.
  3. Select the encryption key.
  4. Click Open.
Backup Exec is unable to import the database encryption key "abcd.dek". Could not find file "c:\key\abcd.dek". If you receive this message, the manual import process failed.

The message should indicate a possible reason for the failure. Resolve the issue, if possible and then attempt to manually import the key again.

If Backup Exec cannot find the key, you can manually copy the database encryption key to the proper directory:
  1. In Windows, browse to the secure location to which you exported the database encryption key.
  2. Copy the .dek file and paste it into the "Data" folder in the directory to which you installed Backup Exec.
  3. In Backup Exec, click Retry on the message dialog to reattempt to recover the key.
Backup Exec is unable to recover the database encryption key "abcd.dek". The path to which the database encryption key "abcd.dek" was exported is unknown. If you receive this message, you exported the database encryption key, but you did not allow Backup Exec to save the path. Since Backup Exec does not know the path to which you exported the key, it cannot automatically recover the key.

You can manually import the database encryption key:
  1. Click Import.
  2. Browse to the directory to which you exported the database encryption key.
  3. Select the encryption key.
  4. Click Open.
Backup Exec is unable to recover the database encryption key "abcd.dek". The database encryption key "abcd.dek" was never exported. If you did not export the database encryption key and you do not have a backed-up copy of the key, contact  Veritas customer support for assistance.
The imported database encryption key is incorrect or corrupt.   If you receive this message, the database encryption key that resides in the "Data" folder in the Backup Exec installation directory is corrupt.

You can manually import the database encryption key:
  1. Click Import.
  2. Browse to the directory to which you exported the database encryption key.
  3. Select the encryption key.
  4. Click Open.

If you can log in to Backup Exec once you have completed the appropriate action, you successfully completed the procedure. Backup Exec now has the proper database encryption key. You should not receive any more messages.

If you receive the message when any operation in Backup Exec fails:

Message Action
The database encryption key is incorrect, corrupt, or missing. Ensure that a valid database encryption key with the name "abcd.dek" is in use and retry the operation. Close Backup Exec and then restart it. If Backup Exec is able to automatically recover the key, you should be able to log in successfully. If the automatic recovery fails, you should manually import the key.
The database encryption key operation failed. If the database encryption key operation failed, you should contact Veritas customer support for assistance.
 

 

References

UMI : V-79-57344-57379 UMI : V-379-58688 Etrack : 3674217 Etrack : 3772969 UMI : V-79-57344-57383

Was this content helpful?