Amazon AWS backup

[SYSADMIT]

Hello,

Soon there will be a project where you have to deploy a new Active Directory domain with domain controllers (DC) in Amazon AWS.

They will be VMs with Windows Server 2019 with the role of domain controller (DC) in Amazon AWS, not Active Directory as a service.

What would be the best way to backup these virtual machines?

I'm worried about the VM-GenerationID issue. VM-GenerationID is incorporated as of Windows Server 2012 so if you step back from a snapshoot or backup a DC, synchronize again correctly.

The point is that when VM-GenerationID is used, it is the restore backup system that contacts the hypervisor (ESXi or Hyper-V) and changes the VM-GenerationID number so that the AD service detects it and synchronizes correctly again.

If the VMs are on Amazon AWS and are rescued from a backup, is VM-GenerationID used?

Thank you!

Xavi.

[HannesK]

Hello,

What would be the best way to backup these virtual machines?

Well "best"... from a Veeam perspective my opinion today: Veeam Agent for Windows with Application Aware Image Processing enabled. Full VM restore with "Direct Restore to EC2". Reason: you can manage everything from the VBR console

If the VMs are on Amazon AWS and are rescued from a backup, is VM-GenerationID used?

It's more a Microsoft than a Veeam question... but yes, the VM-GenerationID does not care about the hypervisor

Best regards,
Hannes