To deploy HCI clusters and the SCP platform, refer to the corresponding user guides. This section describes the precautions in DR scenarios.

Version Recommendation

HCI: V6.10.0R2 and later are recommended. The primary and secondary sites must use the same HCI version. Otherwise, DR cannot be implemented.

SCP: Use the latest version, and make sure that the version can manage HCI clusters.

Precautions

1. It is recommended to use virtual licenses. This avoids USB key loss or damage, which may affect the use of your clusters, and eliminates the need to change the USB key during primary/secondary failovers.

2. To ensure high availability of SCP, it is recommended to deploy SCP in cluster mode or active/standby mode for DR. The cluster mode is preferred over the active/standby mode because the standby SCP node is shut down in active/standby mode, resulting in low resource utilization. In addition, you need to manually complete active/standby failovers in this mode, and failback operations are not supported. To fail back to the active SCP node, you have to redeploy SCP. After a failover, you need to prepare SCP licensing for the standby node.
3. If you deploy SCP in cluster mode, at least three SCP nodes are required, which will occupy large amounts of resources. Therefore, determine the deployment mode at the early stage of your plan. It is recommended to deploy SCP in three clusters to improve its reliability.
4. If SCP can be deployed only on one node due to limited resources, it is recommended to use scheduled backup and create snapshots before maintenance to ensure the reliability of SCP.