Working with key files for encrypted data - SQL Storage Compress

SQL Storage Compress works with encrypted backup files created by SQL HyperBac, and can also create encrypted database files (data files and log files). This topic describes how SQL Storage Compress uses key files with encrypted backup files and database files.

About key files and encryption

When SQL Storage Compress detects a request from a SQL Server instance to read from an encrypted backup file or to work with encrypted database files, it will first check the 'keys' directory on the SQL Server (located at 'C:\Program Files\Red Gate\HyperBac\keys' by default) to look for a valid key file:

If SQL Storage Compress finds a key file, it uses this key file to encrypt and decrypt the data as it passes through the Windows file system
If a key file does not exist, or the wrong key file is present, the SQL Server instance will report an error accessing the associated backup file or existing database files.
When you initially create an encrypted database or backup, if no key file exists, SQL Storage Compress will generate a key file automatically, and place it in the 'C:\Program Files\Red Gate\HyperBac\keys' directory.

You can think of the key file as equivalent to a password for accessing encrypted data. If you lose the key file associated with an encrypted backup file or encrypted database files, the data cannot be accessed or recovered.

Was this article helpful?

Search support