Async Data Protection remote site configuration | Nutanix Community
Skip to main content

Hi,

can anybody please help me on below query….?

 

I need to migrate the VMs from Nutanix cluster to Nutanix cluster

 

While configuring the remote site for Async  Disasterrecovry there i have seen two options are 1.Network Maping and 2. Storage container .

here my doubt is, which vlan i need mention..?

Which storage container need to map…?

Please help me step by step on this..

 

Please find the snap for your reference and this is for only reference not exact one.

kindly acknowledge it ASAP.

 

 

its totally up to you how you want to manage your network and storage on the another cluster lets say 

 

on the primary cluster if VM1 is has network vlan 0 , and storage container name is production 

 

so on the secondary cluster it is totally okay to map with diffent network same applys to container.  

 

just you need to make sure network is reachable . 


 

Hi nishantpanchal thank you for your acknowledgement,

 

Suppose i have a 10 vms with different vlans then how we could maping the networking on both sides..?

 

just you need to make sure network is reachable .

 

reachble means all cvms,ahv and cluster ips should be ping vice versa right..?

 

and two more Questions

1.what about bandwidth…?

2.only i want to migrate the vm from one cluster to another cluster then which options i need to choose while creating schedule according to below snapshot.

 

3.while configuring the remote site i saw two options Backup and Disaster Recovery under the capabilities so,

What is the difference between Backup and Disaster Recovery..?

Which Option should i select when migrating the vms DC to DR..?

 

Kindly acknowledge ASAP.


  1. all host and CVM should be able to take to each other its must for cluster services 
  2. it’s totally okay if you GVM are not taking to CVM ,
  3. when mention GVM should be reachable means let’s say you have application VMs and its working fine on the primary cluster where it is currently once you migrate that VM to another cluster you need make sure network is allow from new setup like g/w should be reachable cause once you migrate the VM to another VM it should work fine
  4. bandwidth , it depends on your network capabilities however you have option the data protection window to limit and schedule 
  5. to map the network you need create subnet on the target cluster following on the primary cluster and then just update in the data protection mapping tab
  6. i think backup is to just keep local snapshot on the same cluster and DR means it will replicate to secondary

 

if you just want to migrate after you finish with the data protection and onces snapshot is available on the DR cluster you just need to click mgirate button from data protection windows and all will be done 

 

i got something below to help you 

 

 


  1. all host and CVM should be able to take to each other its must for cluster services 
  2. it’s totally okay if you GVM are not taking to CVM ,
  3. when mention GVM should be reachable means let’s say you have application VMs and its working fine on the primary cluster where it is currently once you migrate that VM to another cluster you need make sure network is allow from new setup like g/w should be reachable cause once you migrate the VM to another VM it should work fine
  4. bandwidth , it depends on your network capabilities however you have option the data protection window to limit and schedule 
  5. to map the network you need create subnet on the target cluster following on the primary cluster and then just update in the data protection mapping tab
  6. i think backup is to just keep local snapshot on the same cluster and DR means it will replicate to secondary

 

if you just want to migrate after you finish with the data protection and onces snapshot is available on the DR cluster you just need to click mgirate button from data protection windows and all will be done 

 

i got something below to help you 

 

 

  1. all host and CVM should be able to take to each other its must for cluster services 
  2. it’s totally okay if you GVM are not taking to CVM ,
  3. when mention GVM should be reachable means let’s say you have application VMs and its working fine on the primary cluster where it is currently once you migrate that VM to another cluster you need make sure network is allow from new setup like g/w should be reachable cause once you migrate the VM to another VM it should work fine
  4. bandwidth , it depends on your network capabilities however you have option the data protection window to limit and schedule 
  5. to map the network you need create subnet on the target cluster following on the primary cluster and then just update in the data protection mapping tab
  6. i think backup is to just keep local snapshot on the same cluster and DR means it will replicate to secondary

 

if you just want to migrate after you finish with the data protection and onces snapshot is available on the DR cluster you just need to click mgirate button from data protection windows and all will be done 

 

i got something below to help you 

 

 

 


Hello @kondasani ashok 

You need to do it from Prism Central:

https://portal.nutanix.com/page/documents/details?targetId=Disaster-Recovery-DRaaS-Guide-vpc_2023_4:ecd-ecdr-draas-virtualnetwork-pc-c.html