BACKUP CERTIFICATE (Transact-SQL) in the old database.The sequence to restore an encrypted database to a new location is to: If you are restoring the encrypted backup to a different instance, you must make sure that the certificate is available on that instance. The user account performing the restore must have VIEW DEFINITION permissions on the certificate or key. It does require that the certificate or the asymmetric key used to encrypt the backup file be available on the instance that you are restoring to. Restoring the encrypted backup: SQL Server restore does not require any encryption parameters to be specified during restores. Without the certificate or asymmetric key, you cannot restore the backup, rendering the backup file unusable. It is very important to back up the certificate or asymmetric key, and preferably to a different location than the backup file it was used to encrypt. The following are the supported encryption options:Įncryption Algorithm: The supported encryption algorithms are: AES 128, AES 192, AES 256, and Triple DESĮncryptor: A certificate or asymmetric Key To encrypt during backup, you must specify an encryption algorithm, and an encryptor to secure the encryption key. In addition, encryption options can be configured for SQL Server Managed Backup to Microsoft Azure operations, a new feature introduced in SQL Server 2014 (12.x). All storage destinations: on-premises and Window Azure storage are supported. By specifying the encryption algorithm and the encryptor (a Certificate or Asymmetric Key) when creating a backup, you can create an encrypted backup file. Starting in SQL Server 2014 (12.x), SQL Server has the ability to encrypt the data while creating a backup. It includes details of the usage, benefits, and recommended practices for encrypting during backup. This topic provides an overview of the encryption options for SQL Server backups.

Backup sql master