question

JanineBirchHornAdmin-0154 avatar image
0 Votes"
JanineBirchHornAdmin-0154 asked SadiqhAhmed-MSFT commented

MIgrated VM backup fails in Azure Backup

Hi,

We recently ran a fairly complicated VM migration which involved downloading the VHDs locally, in-place upgrading from Windows server 2008 R2 to all the way up to Windows Server 2016 ( as it can't be done in Azure) and we then uploaded the VHDs to a totally different Azure subscription and created a VM linked to the VHDs. This VM needed to be migrated and this seemed an easier option than re-uploading to the original Azure subscription and then having to run a migration.

However, the Azure backup in the new subscription fails and it just says try restarting the com+ service or rebooting the server. I have also totally removed the server from the backup vault and deleted the data (turned off soft delete so it went straight away), then re-added back in and it still fails. It passes the pre-checks but when running a backup it fails.

Does anyone have any advice? IS there some backup extension left in place from the old subscription maybe? How do i clean this up? I can only find details on cleaning up the VM whilst it is still attached to the backup vault.

Thanks in advance



azure-backupazure-virtual-machines-backup
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks, I do have the VM agent installed and i did try uninstalling an re-installing the latest version so it does thave the VM agent installed.

We are using the Recovery Services Vailt to backup the VM, sorry if i used the wrong terminaology in my original post :-)

Regards

Janine

0 Votes 0 ·
SadiqhAhmed-MSFT avatar image SadiqhAhmed-MSFT JanineBirchHornAdmin-0154 ·

@JanineBirchHornAdmin-0154 - The issue needs a further deeper dive technically to understand root cause of the issue. investigation of this issue requires involvement of multiple Azure technical support teams like, Azure backup team, VM availability etc. IMO, this can be better handled as a support request. Recommend you to contact Azure backup technical support team by raising a support request. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

Please feel free to reply if there are any challenges reaching out to Azure technical support team!

0 Votes 0 ·

Thanks, that was my next step after asking here.


1 Vote 1 ·

I've just restarted the Distributed Transaction Coordinator service and then re-ran the backup and it now seems to be working. Its done the snapshot and transferring to the vault. I am a bit confused as i have restarted the server several times and that didn't fix it. Maybe a restart doesn't properly restart this service????

I will see if the scheduled backups continue to run as this one has.

0 Votes 0 ·
SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered

Hello @JanineBirchHornAdmin-0154 - Thank you for reaching out to us and I apologize for the inconvenience this must have caused!

For migrated VM's, VM agent is not installed by default. It needs to be installed manually, post that you can protect that VM to Azure recovery services vault to perform backups.

Please follow the troubleshooting guide - https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-troubleshoot#set-up-the-vm-agent to set up the VM agent.

FYI: Difference between 'Recovery Service Vault' (RSV) and Backup vault (BV)

The first difference between Recovery Services Vault (RSV) and Backup Vault (BV) are the available data sources of each vault.

If you create a new Vault in Azure Backup Center there is a screen that is showing the different available data sources of each vault type:

166451-diff-rsv-and-bv.png

The second difference is: RSV can be used for Azure Backup and Azure Site Recovery data. An BV is for Azure Backup data only.


If the response helped, do "Accept Answer" and up-vote it



diff-rsv-and-bv.png (228.3 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JanineBirchHornAdmin-0154 avatar image
1 Vote"
JanineBirchHornAdmin-0154 answered SadiqhAhmed-MSFT commented

To confirm, restarting the Distributed Transaction Coordinator service has fixed the issue. I've done an on-demand backup and a scheduled backup and they have both worked. I presume when restarting windows is doesn't fully stop and start all services as i had rebooted a few times before trying this. Didn't do a power off/on though.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the update. Glad to know you were able to resolve the issue.

0 Votes 0 ·