JetStream Software

Create a Protected Domain

After all other aspects of JetStream DR have been configured, a protected domain must be set up to contain the VMs that will be protected. A protected domain defines a specific VM or set of VMs within the cluster that will be protected together.

Note: A protected domain must be used for VMs to be protected, even if it is only for a single VM.

  1. To create a protected domain, go to the Protected Domains tab and click the Create Protected Domain button.
    NOTE: If no protected domains yet exist, a pop-up message will be displayed.
  1. Follow the steps in the pop-up dialog box.
  • Beginning with 1. General, enter a name for the protected domain and select a storage site from the drop-down menu.
  • (Optional) Set a priority level for the protected domain by selecting a value from the drop-down menu.

    Priority is a numeric value used to identify and sequence operations of protected domains. Priority values from 1 to 5 can be assigned, with lower numbers having higher priority.

    For failover/failback operations, the priority level number is used to identify which protected domains get failed over / failed back and in what sequence. For example, the Continuous Failover function fails over protected domains in batches. By assigning priority levels to protected domains, the administrator could specify domains assigned priority 1 get failed over together first, followed by domains assigned priority 2, then 3 and so on.

    NOTE: Although the priority level can be specified in the UI during creation of the protected domain, it is specifically used together with the Capacity Planning Tool (CPT) script for the purpose of automating failover and failback operations.
  • Specify a value for “Total estimated data size to be protected.” The minimum value is 200GB. This value reserves an initial amount of space for storing metadata and can be changed as necessary to optimize system performance. Click the Next button.

    FOR EXAMPLE: A good minimum starting point is to use the total amount of disk space of all protected VMs in the cluster.
  • On 2 Primary Site, select a DRVA for the protected domain from the drop-down menu. Any DRVA that was previously configured under the Appliances tab can be selected.
  • Select a storage resource for the replication log store from the drop-down menu.
  • Review the replication log and metadata sizes. Default values will be applied but can be changed, if necessary.

    NOTE: The size of the replication log cannot exceed the total replication log store size minus the metadata size. The minimum allowable size of the replication log store is 15GB.
  • Specify compression options. Compression is initially enabled using default settings. If the option Default Compression is deselected, a menu will appear allowing a specific compression level to be manually specified.
  • Enter values to specify the amount of GC Storage Overhead to be reserved for normal garbage collection and a maximum amount that should never be exceeded. The values are represented as percentages of the amount of storage reserved for protected data (described above). The values can be changed as necessary to optimize system performance.

    NOTE: The default maximum amount is 300% (i.e., three times the amount of storage reserved for protected data.)
  • Identify the primary site datacenter and the cluster to be protected. Only clusters that have been configured in the previous steps will appear in the selection drop-down list. Click the Next button.
  • On 3 Summary a protected domain summary screen will appear. Review the settings then click the Create button.
  1. The protected domain will be created. Configuration is now complete and protection of VMs in the cluster can begin.
Was this article helpful?

Need Support?

Can't find the answer you're looking for?
Contact Support