You can deploy a VMware Cloud on AWS recovery SDDC and configure it as a site for both disaster and ransomware recovery.

You can deploy recovery SDDCs using i3en, i3n, and i4i hosts. When you deploy a recovery SDDC, it must be attached to at least one cloud file system, but can be associated with up to four (for high capacity environments).

In addition to deploying a new recovery SDDC in VMware Live Cyber Recovery, you can also add an existing SDDC for recovery. For more information, see Add an Existing SDDC. Once you deploy a VMware Cloud on AWS in a recovery region, it cannot be used in another recovery region.

In order to deploy a new SDDC for recovery, ensure that VMware Live Cyber Recovery has been authorized to connect to VMware Cloud on AWS. For more information, see Authorize VMware Live Cyber Recovery.

Deploying a recovery SDDC is restricted by the following caveats:
  • VMware Cloud on AWS recovery SDDCs are restricted by VMware Cloud on AWS configuration limits. For example, if you want to know the currently supported maximum number of hosts per cluster, the maximum number of SDDCs per region, or the maximum number of SDDCs per Organization, and more, see VMware Configuration Maximums.
  • vSAN Express Storage Architecture (ESA) Preview is not supported for recovery SDDC. If vSAN ESA Preview is enabled on your recovery SDDC, you cannot perform disaster or ransomware recovery operations.
  • Stretched clusters are not supported for recovery SDDCs.
  • If you need PCI hardening for your recovery SDDC, contact VMware Support for assistance.
Important: For more information about VMware Live Cyber Recovery configuration limits, visit the VMware Configuration Maximums tool.