Sangfor Cloud Platform (SCP)

Enterprise Cloud Computing Platform Built on Business-Centric HCI.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
Sangfor Cloud Platform (SCP) {{ breadTitle }} Primary-Secondary Disaster Recovery Installation and Deployment SCP Deployment in Active/Standby Mode (Optional)
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","SCP Deployment in Active/Standby Mode (Optional)")}}

SCP Deployment in Active/Standby Mode (Optional)

{{ $t('productDocDetail.updateTime') }}: 2025-12-18

Introduction

SCP can be deployed in active/standby mode to improve its reliability, which is suitable for cross-site DR. The active SCP node is deployed in the cluster located on the primary fault domain, and the standby SCP node is deployed in the cluster located on the secondary fault domain. When the primary fault domain is down, the active SCP node becomes unavailable. You can manually fail over to the standby SCP node. The standby node serves as the active node to ensure the high availability of SCP. You can fail over to the standby node only when the active node is down.

Precautions

  1. Make sure that the IP addresses of SCP do not conflict with the IP addresses of other VMs. In addition, the network connectivity between the active and standby SCP nodes is normal.
  1. After an active/standby failover, the standby SCP node is restarted and then functions as the active SCP node.
  2. When you access the new active node after a failover is complete, the system prompts that the USB key is unplugged and the license is about to expire. To address this issue, map the USB key to the new active node within 30 days, redeploy the SCP VMs on the active node, and add the new SCP node as the standby node.
  3. If SCP is deployed in active/standby mode and the active SCP node is deployed in cluster mode, the original SCP cluster can no longer be used after the role of the remote standby node is switched to active. This helps avoid the issue of two active nodes. In addition, the remote standby node will recover the business in standalone mode.

Prerequisites

The HCI platform and SCP VMs are deployed as expected.

Procedure

  1. Deploy SCP as a new deployment.
  1. Log in to the active SCP node and go to Resources > Reliability > Platform Status Check > SCP Failover.

  1. Click New, enter the IP address and password of the SCP standby node, and click OK.
  2. After the node is added, you can view the status of the active and standby nodes.
  3. You can manually remove the standby node. When the active node is disconnected, you can log in to the standby node and switch its role to active.