In some situations, you may need to reconfigure a backup job that processes a Microsoft SQL Server VMs and ships transaction logs. For example, you may want to create a separate backup job to process the virtualized database, and delete the VM running the database from the previously created job.
When you configure a new job, mind the restriction on transaction logs shipping.
By default, the new backup job that processes the VM will not ship transaction logs if transaction logs for this VM have been shipped for the last 7 days by another backup job on the same backup server. To overcome this restriction, you can reconfigure the backup jobs.
The procedure below is required only if you do not want to delete the initial backup job.
- Remove the Microsoft SQL Server VM from the initial backup job.
As an alternative, you can disable transaction logs shipping in the job properties: in the guest processing settings, select the Do not truncate or Perform copy-only option.
- In the registry on the backup server, locate the SqlBackupLogsAgeDaysToSkipLogBackup registry key and set its value to 0
delete transaction logs for the Microsoft SQL Server VM from the backup repository.
- Create a new backup job to process the Microsoft SQL Server VM and enable transaction log shipping in the job properties.
- It is strongly recommended that you delete the SqlBackupLogsAgeDaysToSkipLogBackup registry key in a week. In this case, if the VM is added to several jobs, transaction logs will not be shipped to different backup repositories.