If you are protecting an SDDC and want to expand its capacity, you can set up an additional protected site for it with a new cloud file system for extra capacity.
In some cases, you need to expand you protected capacity but do not want to deploy a second SDDC. To scale capacity for a protected SDDC, you can create an additional protected site and then use separate cloud file systems for each site to expand capacity.
For example, you have one protected SDDC with a single vCenter connected to its own cloud file system. You an create an additional protected site for it, register the site to the same vCenter, and then connect the second site to a different cloud file system, shown here:
Before You Set Up an Additional Protected SDDC
If your recovery SDDC is in the same AWS region as your protected SDDC, each cloud file system must be deployed to a different availability zone (AZ) than the the AZ where the recovery SDDC is deployed.
All cloud file systems must be deployed before you can connect them with a new protected SDDC.
The network connection configuration for the new protected site must be the configured the same for the original protected SDDC. If the initial protected SDDC firewall was configured manually, then you must manually create the same firewall rules on the second protected site.