Knowledge Base

Search Knowledge Base

KB #240072 : Log Shipping with Encryptionizer (driver v2008.401.40 and earlier)




Log Shipping is supported with the procedure outlined below, and only with Encryptionizer 2007 or later(v2007.101.15). With Encryptionizer versions 2007.101.15 through 2008.401.40, Log shipping is supported when the shipping logs are encrypted with our proprietary LLE 256 algorithm. (You can still encrypt your databases themselves with all the algorithms available through NetLib (AES, 3DES, Blowfish, LLE).Encryptionizer 2012 (driver v2010.201.10 and later) supports Log shipping at AES 256 bit level. Please see related article.

Additional Information:

SQL Log shipping is supported using Encryptionizer version 2007.101.15 or later.

If you have Encryptionizer versions 2007.101.15 to 2008.401.40 you will use the procedure below. For Encryptionizer versions 2010.201.10 and later, you can use AES 256bit Encryption using the method described in the following article: KB240103: Log shipping with Encryptionizer (driver v2010.201.10 and later).

Using the Admin Wizard on the primary machine:

  • Add your database key(s) on the Enable Encryptionizer screen. Add one additional key using the LLE 256 algorithm and note the Key number assigned in the list. This last key (Key N) will be assigned later for use with the shipping logs.
  • Set the option to “Encrypt New Databases and Backups” on the Additional Options screen
  • Choose the “Specify File Names to include/exclude” feature. Set Key N (from the step above) to be used with the shipping log file extension (*.trn , Include , 1). (If you need to also encrypt newly created databases and backups, see the Whole Database User Guide for more detailed instructions.)

On the primary machine, using the Encrypt/Decrypt Wizard, encrypt the database files using an encryption key profile that matches one of the encryption keys set in the Admin Wizard (except Key N).

Set up the backup machine with the identical settings.

Related Topics:

240103: Log Shipping with Encryptionizer (driver v2010.201.10 and later)

Last modified: 1/29/2016