Expertise for Hypervisors Migration to IaaS
Budget: $15 – $25 USD
We are migrating our on-prem Hypervisors (legacy VMware vSphere) to a Cloud Hosted IaaS solution. We are mid-way through the process and have identified a potential problem that could arise during the cutover phase which we need help with.
In brief we have 3 domain controllers, they are configured as seen here:
DC1 - On-prem - Windows Servers 2012 R2 | DHCP, DNS & All FSMO roles
DC2 - On-prem - Windows Servers 2012 R2 | DHCP, DNS
DC3 - Azure Cloud - Windows Servers 2019 Standard | DNS
During the IaaS cutover DC1 and DC2 will be shut from between 12 to 24 hours, and then restored into the new IaaS environment, DC3 will stay in Azure and stay online while this happens.
The restore of DC1 + DC2 will be performed as a normal VM restore (using Veeam Service Provider Console Agent) without the option to select a non-authoritative or authoritative restore.
When DC1 and DC2 are restored in this way we are concerned this could cause replication issue between DC1, DC2 and DC3 after the restores are complete, for example related to:
USN Rollback, if the restored DCs have outdated update sequence numbers (USNs) or SYSVOL replication Issues or even FSMO role conflicts.
We need professional advice on how to best mange this situation avoiding any pitfalls. Good communication and preferably experience from similar situation is preferred. You will be communicating primarily with a Project Engineer and potentially the IT manager of the business
In brief we have 3 domain controllers, they are configured as seen here:
DC1 - On-prem - Windows Servers 2012 R2 | DHCP, DNS & All FSMO roles
DC2 - On-prem - Windows Servers 2012 R2 | DHCP, DNS
DC3 - Azure Cloud - Windows Servers 2019 Standard | DNS
During the IaaS cutover DC1 and DC2 will be shut from between 12 to 24 hours, and then restored into the new IaaS environment, DC3 will stay in Azure and stay online while this happens.
The restore of DC1 + DC2 will be performed as a normal VM restore (using Veeam Service Provider Console Agent) without the option to select a non-authoritative or authoritative restore.
When DC1 and DC2 are restored in this way we are concerned this could cause replication issue between DC1, DC2 and DC3 after the restores are complete, for example related to:
USN Rollback, if the restored DCs have outdated update sequence numbers (USNs) or SYSVOL replication Issues or even FSMO role conflicts.
We need professional advice on how to best mange this situation avoiding any pitfalls. Good communication and preferably experience from similar situation is preferred. You will be communicating primarily with a Project Engineer and potentially the IT manager of the business