Solved

Multiple Source Protection Domains Pointing to the Same Remote Site?

  • 8 February 2016
  • 1 reply
  • 1840 views

Badge +5
I'm fairly certain this is possible, but going is rough for finding it documented. Let's say I have a remote container setup in a NTX cluster in LA. Can I created protection domains in a NTX cluster in Miami and NewYork and point them both to the remote container in LA? Sort of a many to one type approach in using protection domains and any limits on how many you can point at one? Any documentation anyone's found covering this and docs on where the snaps are stored (I don't see them in the ESXi datastores) and how much data is used from remote snaps.

Thanks!
icon

Best answer by cbrown 8 February 2016, 17:15


Yes, that is fully supported. The only system limits we have are published here:

https://portal.nutanix.com/#/page/docs/details?targetId=Web_Console_Guide-Acr_v4_5:app_system_maximums_r.html

You would create 2 remote containers in LA (one for NY, one for Miami) and LA should be licensed with Ultimate (http://www.nutanix.com/products/software-editions/) to get the many-to-one feature. The other sites can be licensed at any level. You'd then setup the vstore mappings on the each site to their unique container.

Snapshots are stored in the .snapshot directory on the container. The space they use is variable, but it depends heavily on the size of the VMs you're protecting, the rate of change of those VMs, and the number of snapshots you retain (and any data-reduction tech you're using such as compression/EC-X)
View original

1 reply

Userlevel 3
Badge +16
Yes, that is fully supported. The only system limits we have are published here:

https://portal.nutanix.com/#/page/docs/details?targetId=Web_Console_Guide-Acr_v4_5:app_system_maximums_r.html

You would create 2 remote containers in LA (one for NY, one for Miami) and LA should be licensed with Ultimate (http://www.nutanix.com/products/software-editions/) to get the many-to-one feature. The other sites can be licensed at any level. You'd then setup the vstore mappings on the each site to their unique container.

Snapshots are stored in the .snapshot directory on the container. The space they use is variable, but it depends heavily on the size of the VMs you're protecting, the rate of change of those VMs, and the number of snapshots you retain (and any data-reduction tech you're using such as compression/EC-X)

Reply