none
Change in Domain for Configuration/Process server and impact RRS feed

  • Question

  • Hey ,we are planning to migrate on-prem Vm's to Azure , also we are migrating or consolidating our internal AD domain i.e. domain b , c to Domain A to one domain, target domain A already extended to azure

    now we have two scenarios to migrate, please suggest pros and cons for both scenarios

    1 . install and configure ASR on current local AD domain>Replicate to blob>move replicated VM to target domain along with ASR servers

    Q . will there be any impact on replication or while doing fail over.

    2. start install and configure of ASR , once all server and domain consolidation is done.?

    comment : this will be the safest and straight forward implementation


    Ragav

    Tuesday, September 10, 2019 4:38 AM

All replies

  • 1. You can configure ASR for your local AD domains and replicate to Azure. The replication will happen and you would be able to failover. However, you cannot login as a domain admin if there is no connectivity between your on premise local AD to Azure VM's. So, basically you need to set up site-to-site VPN in this situation.

    2. Your second option would be best for this scenario.

    Tuesday, September 10, 2019 11:37 AM
    Moderator
  • Hey Sadiq , am  re-summarizing my 1st question

    Lets assume , I have deployed Config/process server on-premises for domain C and B, and source VM's are protected in azure blob

    Now we have AD consolidation for on-premises  for domain C and B will be moved to domain A, where VM from domain C and B will be moved to domain A .

    while source VM from domain C and B domain get changed will there be any impact on replication or protected copy

    And in azure we have already domain A working including connectivity.

    we want to know the impact of domain change on source VM for already protected VM in azure

    And we are considering second option as Plan B ,


    Ragav


    Tuesday, September 10, 2019 1:14 PM
  • When you are changing the domain it doesn't have any impact though you need to take care of some stuff:

    1. Make sure your hostname exists the same.

    2. Make sure you domain changed VMs are reachable to the configuration server.

    3. A reboot is required for the domain changed VM, which may mark for the re-sync if hard reboot might happen which can trigger to re-sync the changes again or if it's a soft reboot it should not impact the replication.

    4. Configuration server is a domain independent, until source Vms are reachable.

    5. Time Sync is the major problem, as agent communicates based on it to generate consistent points.

    Finally I would suggest to make domain change for one of the least impact-able VM and cross-check the replication and do a test failover(if possible) once and verify the above points.

    Outcome:

    1. Replication should be working as expected.

    hope you are not changing the vCenter or ESX for this?

    • Proposed as answer by Mara Ram Wednesday, September 11, 2019 6:46 AM
    • Edited by Mara Ram Wednesday, September 11, 2019 6:47 AM
    • Unproposed as answer by Mara Ram Wednesday, September 11, 2019 6:47 AM
    Wednesday, September 11, 2019 6:46 AM