![]() Use customer-managed key stored in Azure Key Vault (AKV) instead to protect the database and enable access to the same key from the destination SQL Server 2022 instance. If you’re using a service-managed key for data protection at rest, the key is not available outside of the instance and taking copy-only full backup is preventively blocked. Restoring a backup of an encrypted databaseįor databases encrypted at rest by using Transparent Data Encryption (TDE), the destination SQL Server 2022 instance must have access to the protector key used on the source managed instance to be able to read the data from the backup file. Once a backup file is created, you can download it locally or to a shared location before restoring it, or you can simply restore it directly from the storage account if the storage account is accessible from the destination SQL Server:įigure 1: Using T-SQL to back up SQL MI database to Azure Storage and restore it to SQL Server 2022įor detailed instructions check the how-to article. It enables you to provide a copy of a SQL MI database to your end users or eligible third parties for regulatory compliance and other purposes to use it as a light-weight business continuity and disaster recovery solution for restoring functionality on another instance of SQL Server or simply for seeding or refreshing your other SQL Server environment.Ĭopy-only backups of SQL MI database are stored in Azure Blob Storage account that you provide as part of the backup command. Now generally available, this capability significantly improves the freedom of data movement across SQL estates. ![]() We are excited to announce that you can now restore a copy-only full backup of an Azure SQL Managed Instance (SQL MI) database to an instance of SQL Server 2022 hosted anywhere. Restoring a backup file is the easiest way to copy a database to another instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |