Important notices for system administrators:

  • Virtual Machines must be located on shared storage. All datastores, on which VMs to be protected are located, must be accessible from all hosts in a cluster.
  • Enabling DRS is strongly recommended for protected and recovery clusters because it is required for DR components HA and to uninstall or upgrade JetStream software.
  • The JetStream DR management console supports single client access only. Otherwise, configuration changes may be reflected incorrectly in the GUI.
  • Do not make changes to the configuration of any JetStream DR component (i.e., virtual appliances automatically created during Failover, Failback, Restore, and PITR recovery) in a way other than by utilities provided by JetStream.
  • When using the GUI to configure a cluster, installation may fail, and storage policies will not be created on the vCenter server. This is a VMware limitation.
  • Failover and Failback wizards have a VM “Storage Policy” drop-down option during task submission. This is an optional selection and if not specified, the datastore default policy will be used. However, in some environments the default policy could be inappropriate. An appropriate policy must be selected based on the target environment. Specifically, when selecting VSAN RAID FTT, refer to VMware VSAN documentation for policies and ESXi node requirements to make sure the target environment can support those RAID policies (for example, has appropriate number of hosts).
  • VMware has officially stopped supporting vSphere 6.7. However, if vSphere 6.7 is currently being used, it is possible to try JetStream DR software for PoC purposes before switching to vSphere 7.0 for production. JetStream DR can run on vCenter 6.7 U1 (build 10244745) and above with ESXi 6.7 PO3 (build 16713306) and above, with IOFilters manually installed on all hosts for PoC. However, JetStream DR cannot be used for production with 6.7 vCenter and ESXi.
  • The number of virtual disks from all VMs in all domains that are protected under a single DRVA should not exceed 500.
  • When starting RCR user is not forced to enter RocVA network parameters on resume recovery side, so default networking configuration would be: all network selection will be same as DRVA, all interfaces will use DHCP, and Object Store network will be selected as the default gateway. (DRBC-7590)
  • After an MSA is registered with vcenter, it must not change IP/FQDN under which it was registered. If the change is required, unregister MSA, change IP, then register again.
  • MSA ships python 3.6 for runbook scripts. It will be updated to Python 3.9 in future releases. (DRBC-7338)