Skip to content

Commit 1305e1b

Browse files
author
David Curwin
committed
Move VM to new RG
1 parent 8829fb9 commit 1305e1b

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

articles/backup/backup-azure-vm-backup-faq.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,14 @@ The VM is backed up using the schedule and retention settings in the modified or
171171

172172
You can restore the VM from available restore points that were created before the move operation.
173173

174+
### What happens after I move a VM to a different resource group?
175+
176+
Once a VM is moved to a different resource group, it's a new VM as far as Azure Backup is concerned.
177+
178+
After moving the VM to a new resource group, you can reprotect the VM either in the same vault or a different vault. Since this is a new VM for Azure Backup, you'll be billed for it separately.
179+
180+
The old VM's restore points will be available for restore if needed. If you don't need this backup data, you can stop protecting your old VM with delete data.
181+
174182
### Is there a limit on number of VMs that can be associated with the same backup policy?
175183

176184
Yes, there's a limit of 100 VMs that can be associated to the same backup policy from the portal. We recommend that for more than 100 VMs, create multiple backup policies with same schedule or different schedule.

0 commit comments

Comments
 (0)