Azure-docs: Is the Azure Backup section still valid?

[badbob001]

Last year, classic VMs were automatically migrated from Backup Vaults to Recovery Services. Recovery Services refer to classic VMs by their Resource Group assignment, so post migration, if the Resource Group assignment doesn't change and the backup extension is re-installed, then would the existing backup protection still work?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7e62fa0e-b3db-03a0-30ed-d280fa022219
• Version Independent ID: 1037cec6-8878-85ca-e0d4-b7a0c2fdb4cf
• Content: Frequently asked questions about Classic to Azure Resource Manager migration
• Content Source: articles/virtual-machines/windows/migration-classic-resource-manager-faq.md
• Service: virtual-machines-windows
• GitHub Login: @singhkays
• Microsoft Alias: kasing

[mimckitt]

Thanks for the question! We are investigating and will update you shortly.

[mimckitt]

@badbob001 we are working offline to get an answer to this question. Will update you once we have more information.

[mimckitt]

@badbob001 Just to confirm, you are still using classic VMs right? However rather than backup everything is stored in Recovery Services

[badbob001]

Hi,
Yes, I'm still using Classic VMs. They use to be connected to the Backup
Vaults but MS transparently migrated everyone to Recovery Services. So no
one should be using Backup Vaults anymore and thus their mention in the FAQ
is irrelevant.

Now that Classic VMs are assigned to Recovery Services, I see that the VM
registrations refer to the VM's Resource Group and not their Cloud Service.
Often the Resource Group and Cloud Service are named the same, but not
always. I was hoping that after the migration, I just need to install the
new backup extension and the VMs will continue to backup using their
original registration. But I just read that migrated VMs are assigned to a
new Resource Group, named -migrated, and the VM's
previous Resource Group is ignored. So if the VMs' Resource Groups are
changing, then all the backup registration will no longer be valid and I
will need to manually re-register all my migrated VMs to backup (a lot of
work). Please let me know if this information is still correct.

Thanks,
Robert

On Wed, Jul 25, 2018 at 12:56 PM Micah [e-mail] wrote:

@badbob001 https://github.com/badbob001 Just to confirm, you are still
using classic VMs right? However rather than backup everything is stored in
Recovery Services

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/12287#issuecomment-407823762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAzEJ-PDMmNfiq6LOvLKlkyLApgHs_RDks5uKKNMgaJpZM4Vc7mv
.

[mimckitt]

Got it! Thank for clarifying that for me. I am working offline to get an answer to this. Will update shortly.

[mimckitt]

@singhkays can you take a look at this document and ensure it still makes sense? As well as chime in on this issue

[GavinEke]

Hi,

I have gone through the process to stop the backup as mentioned in the article, I think some of the wording might be outdated such as all of 2. 'Click Stop Protection. Leave Delete associated backup data option unchecked.' I believe it is now 'Stop Backup' instead of 'Stop Protection' and it is no longer a tickbox it is now a dropdown menu but even after completing these steps when I go to validate migration from Classic IaaS to Resource Manager I still get the following error message:

VM server01 in HostedService server01 is currently configured with the Azure Backup service and therefore currently not supported for Migration. To migrate this VM, please follow the procedure described at https://aka.ms/vmbackupmigration.

Can this be looked into.

Kind Regards,
-Gavin

[TroyArrandale]

I have the same issue as GavinEke - can't migrate as the backup services options are no longer available and it fails validation on "Migrate to ARM".. can we get an update on this?

[Karishma-Tiwari-MSFT]

@singhkays v-thepet Can either of you please share who would be the right person to help this doc getting updated? Thanks :)

[kaiserguy]

I have the same issue - can't migrate as the backup services options are no longer available and it fails validation on "Migrate to ARM".. can we get an update on this?

[kaiserguy]

I was able to migrate after removing the backup extension from the VM.

[mimckitt]

Yes you need to remove the backup prior to performing the migration.

I will add a note to this doc.

[mimckitt]

Actually, the doc is correct.

To migrate the virtual machine to Resource Manager mode,

Delete the backup/snapshot extension from the VM.
Migrate the virtual machine from classic mode to Resource Manager mode. Make sure the storage and network information corresponding to the virtual machine is also migrated to Resource Manager mode.