An Azure relational database service.
Backup data can’t be moved from one Recovery Services vault to another. To protect the SQL databases in a different vault, configure backup again in the new vault; the old backup data remains in the original vault.
For preserving backups in the old vault:
- Backup data in the original vault can be retained even after protection is stopped by using Stop protection with retain data. The existing recovery points remain and can be used for restore as long as they are not expired or deleted.
- Retained data in the old vault continues to incur backup charges while it exists.
- Backup data stored in a vault isn’t automatically soft-deleted just because the protected resource is moved or backup is reconfigured elsewhere. Soft delete applies when backup items or vaults are deleted; items then stay in a soft-deleted state for the configured retention period and can be recovered during that time.
- If backup is stopped with retain data (and the item isn’t deleted), recovery points remain as normal backup data and follow the last active policy’s retention behavior, similar to VM backups.
For SQL Server in Azure VMs specifically:
- When the VM is moved (for example, across regions or resource groups), SQL backups in the old vault do not automatically move. The VM must be re-registered and SQL backups reconfigured in the new vault.
- The backup data for the “old” VM/SQL databases in the original vault remains and can be restored (for example, via alternate location recovery) as long as the recovery points are retained.
So, behavior is aligned with VM backups: data in the old vault can be preserved and used for restore until deleted or expired per retention, and soft delete only comes into play when items/vaults are deleted.
References: