Skip to main content

Manage stateful failover

In RBAC mode, only the system administrator can configure this feature.

Stateful failover enables management platform to switch services to the backup management platform host when the primary management platform host fails to avoid service interruption. The primary management platform host synchronizes database files to the backup management platform host through the management network in real time. You can create a local synchronization partition on the primary management platform host to synchronize data other than database files to the backup management platform host.

Prerequisites

Make sure the two hosts for stateful failover meet the following requirements:

• The hosts use a new system, without any incorporated CVK hosts or VMs.

• The hosts have only two storage pools isopool and defaultpool.

• The hosts use the same NSphere version and boot mode, and must have the same NSphere components management platform installed.

• The system time offset between the two hosts is not greater than 5 minutes.

• The /vms partition has at least 20G storage space.

• The management networks of the two hosts are reachable to each other.

Restrictions and guidelines

• To have management platform hosts join the management platform as CVK hosts after the stateful failover system is set up, make sure the system is a newly installed system.

• Do not perform primary/backup switchover when the backup host is in abnormal state, data is being synchronized, or data synchronization is in abnormal state.

• Whether a primary/backup switchover can succeed depends on whether the data has been synchronized from the primary host to the backup host.

• The primary node IP, backup node IP, and VIP must be on the same Layer 2 network.

Set up a stateful failover system

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Set Up Stateful Failover System.

  4. Configure the parameters as described in "Parameters."

  5. Click OK.

Display stateful failover settings

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover. The page that opens displays the host name, status, and settings.

Perform manual primary/backup switchover

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Primary/Backup Switchover.

  4. In the dialog box that opens, click OK.

Bulk edit host passwords

Perform this task to edit the password of hosts connected to the management platform. After editing a host password, the corresponding user's password on the host will also be updated. Note that hosts already managed by other management platforms do not support this operation.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Edit the host password as follows:

    ○ To edit the password for one or multiple hosts in bulk, select the hosts, and click Bulk Edit.

    ○ To edit the password for a single host, click Edit in the Actions column for that host.

    ▪ Username: Username used by the system to access the host via SSH, which cannot be edited. If the ROOT SSH permission is enabled, only the root user is supported. If the ROOT SSH permission is not enabled, only the sysadmin user is supported.

    ▪ Password: Enter the new password of the root or sysadmin user. To view examples of common invalid passwords, click View Common Invalid Passwords.

    ▪ Confirm password: Enter the password again for confirmation.

  4. Click OK.

Display stateful failover host information

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover. If the management platform host is not added to management platform as a CVK host, the system displays the Networks, Storage Adapters, and Routes tabs for the management platform host.

  3. Manage the vSwitches of the management platform host on the Networks tab. You can add, edit, or delete vSwitches.

  4. Manage the storage adapters of the management platform host on the Storage Adapters tab. You can edit the IQN or scan storage devices.

  5. Manage the routes of the management platform host on the Routes tab. You can add, edit, or delete route settings.

Parameters

Stateful failover system setup

• Virtual IP Address: Specify the IP address for accessing management platform. It must be an IP address not in use.

• Mask/Prefix: Specify the subnet mask or prefix for the virtual IP address.

• Backup Host IP Address: Specify the management IP address of the backup management platform host.

• Backup Host Root PWD: Enter the root password of the backup management platform host.

• Quorum Mode: Select a quorum mode. Options include Advanced and Ping.

○ Advanced: Specify a CVK host as the quorum host. When the primary and backup management node cannot communicate with each other, they send their respective state information to the quorum host. The quorum host determines the role of each node and sends the role information to the nodes. The NSphere software versions of the quorum host and primary and backup management platform hosts must be the same.

○ Ping: Specify two quorum IP addresses. When the primary and backup management node cannot communicate with each other, they ping the quorum IP addresses. If a node fails to ping any quorum IP address, the node determines that it has network failures and becomes a backup node.

• Quorum Host IP Address: Specify the IP address of the quorum host. The quorum host must have the CVK component installed.

• Quorum Host Root PWD: Enter the root password of the quorum host.

• Quorum IP Address: Specify the IP address of a gateway that can be accessed or the IP address of a host that is always reachable as the quorum IP address. The quorum IP address is used to check the network connectivity of the management nodes. As a best practice, specify the IP address of a gateway. You must specify two different quorum IP addresses if you select the Ping quorum mode.

• Database Partition Size: Specify the database partition size. The database partition is used for data synchronization between the primary and backup management nodes and is part of the /vms partition. To calculate the database partition size, click Estimate Used Storage Space on the System Parameters > Performance Monitoring Parameters page. For more information, see "Configure system parameters.".As a best practice to reduce the stateful failover setup time, use 10GE fiber cables to connect the management networks of the two management platform hosts when the database partition size is greater than 200 GB.

Network:

• Name: Name of the vSwitch.

• Network Type: Select network types for the vSwitch.

○ Mgmt—Network for transmitting control layer data between management platform and hosts.

○ Service—Network for transmitting service data of VMs.

○ Storage—Network for transmitting data between hosts and IP SAN storage servers or distributed storage. This type of vSwitches cannot be used by VMs.

○ Backup—Network for transmitting backup data between VMs and remote servers. A host can have only one vSwitch or subnet of this type and the vSwitch cannot be used by VMs.

○ Migration—Network for transmitting memory and disk image data for VM migration. A host can have only one vSwitch or subnet of this type and the vSwitch cannot be used by VMs.

• Forwarding Mode: Select the forwarding mode of the vSwitch.

○ VEB—Virtual Ethernet Bridge (VEB) mode. In this mode, the vSwitch forwards traffic based on software.

○ VXLAN (SDN)—Forwarding mode provided by the VXLAN solution based on SDN controllers and cloud computing management platforms.

• VLAN ID: Specify a VLAN ID for the local port of the vSwitch. You can use VLAN to isolate host traffic from VM traffic at Layer 2.

• MTU: Set the maximum packet length allowed by the vSwitch, in bytes. You can specify the vSwitch MTU of the current network as the default MTU. The default MTU of that network on the System > Parameters > Network Settings page will be replaced automatically. The MTU of vSwitch vswitch0 cannot be changed.

• Multicast: Enable multicast forwarding for the vSwitch. You cannot enable multicast for vSwitch vswitch0. This parameter is available only if you select the service network type.

• Micro-Segmentation: Configure whether to enable micro-segmentation or not. If you enable micro-segmentation, the vSwitch will redirect the traffic of isolated VMs to a redirection vSwitch. To isolate VMs with microsegments, you must enable micro-segmentation. This parameter is available only if you select the service network type.

• Acceleration Mode: Select an acceleration mode for the vSwitch. This parameter is available only if you select the service network, storage network, backup network, migration network, or mirroring network type.

○ Common: In this mode, advanced settings are not enabled.

○ DPDK: This mode can improve the network performance of the vSwitch. You must first enable DPDK in the advanced settings for the host attached to the vSwitch.

• Physical Interface: Name of the interface on the physical NIC assigned to the vSwitch. A physical interface can be assigned to only one vSwitch. When all physical interfaces of the host are assigned to vSwitches, this parameter is not configurable. If the vSwitch is not assigned a physical interface, VMs attached to the vSwitch can communicate only with each other but cannot communicate with external networks. If you specify multiple physical interfaces for the vSwitch, you must configure the link aggregation mode and LB mode.

• Use Existing Networks: If you select this option, a vSwitch can share a physical interface with other vSwitches for resource sharing. vSwitches with the same acceleration mode can share the same physical interface.

○ A vSwitch can use the physical interface of other vSwitches only when its network type is Service, forwarding mode is VEB, and acceleration mode is Common or DPDK.

○ The physical interface of a vSwitch can be used by other vSwitches only when its network type is Management, Migration, Backup, or Storage, forwarding mode is VEB, and acceleration mode is Common or DPDK.

○ To configure IP information or subnets, set them on the vSwitch whose physical interface is used by other vSwitches.

○ One physical interface can be shared by up to four vSwitches.

• IPv4 Address: Enter an IPv4 address for the vSwitch.

• Subnet Mask: Enter the subnet mask of the IPv4 address.

• IPv4 Gateway: Enter an IPv4 gateway for the vSwitch. A host can have only one IPv4 gateway.

• IPv6 Address: Enter an IPv6 address for the vSwitch.

• Prefix Length: Enter the prefix length of the IPv6 address.

• IPv6 Gateway: Enter an IPv6 gateway for the vSwitch. A host can have only one IPv6 gateway.

• LAGG Mode: Set the link aggregation mode of the physical NICs. Options include Static and Dynamic. If dynamic link aggregation mode is used, you must enable LACP on the physical switch. This mode is configurable only when multiple physical interfaces exist.

• LB Mode: Set the load balancing mode of physical NICs. This parameter is configurable only when multiple physical interfaces exist.

○ Advanced—Performs load balancing for packets based on the Ethernet type, IP protocol, source IP address, destination IP address, source port number, and destination port number.

○ Basic—Performs load balancing for packets based on the source MAC address and VLAN tag.

○ Active/Standby—Performs load balancing for packets based on the primary and backup roles of physical NICs. If the primary NIC fails, traffic is automatically switched to the backup NIC.

• Fallback: Select whether to switch services from the backup NIC back to the primary NIC after the primary NIC recovers from a fault. This parameter is available only if you select the service or mirroring network type and the load balancing mode is set to Active/Standby.

• Primary NIC Selection: Select the method used to select the primary NIC. This parameter is available only if you select the service or mirroring network type and the load balancing mode is set to Active/Standby.

○ Rate-Based—The system automatically selects the primary NIC based on the rates of the NICs. The NIC with the highest rate becomes the primary NIC. When multiple NICs have the same rate, the system randomly selects a NIC as the primary NIC.

○ Manual—Specify the primary NIC by arranging the LB priorities of the NICs. The NIC with the highest priority is the primary NIC. You must configure the LB priorities for the NICs in this mode.

• LB Priority: Arrange the physical interfaces to define their LB priorities. The physical interface on the top has the highest priority and is the primary physical interface. This parameter is available only if you select the service or mirroring network type, the load balancing mode is set to Active/Standby, and the primary NIC selection method is manual.

• State: State of the vSwitch.

• IP: IP address of the vSwitch.

• Mask/Prefix: Subnet mask of the IP address.

• Gateway: Gateway of the vSwitch.

• Type: Type of the vSwitch.

• DPDK State: DPDK state of the vSwitch.

Storage adapter

• Name: Storage adapter name.

• Model: Storage adapter model.

• Type: Storage adapter type.

• State: Storage adapter state.

• IQN: Storage adapter identifier.

• Normal Scanning: Scans devices by following normal scanning rules.

• Forced Scanning: Forcibly scans devices. New devices can be detected only through forced scanning (resetting storage links) for some HBA cards. This operation might cause I/O timeout.

Route

• Dest Subnet: Subnet of the destination IP address.

• Dest Mask/Prefix: Subnet mask or prefix of the destination IP address.

• Gateway: Gateway IP address of the host.

Manage template pools​

A VM template pool enables you to save VM templates to be deployed to a specified storage pool. This

feature not only simplifies the search and deployment process of VM templates but also allows sharing of VM templates across different environments.

Restrictions and guidelines

• Before you configure an NVMe-oF template pool, configure lossless network settings. For how to configure lossless network settings, contact Technical Support.

Add a template pool

You can create a dedicated storage pool path for VM templates. As a best practice to save management network bandwidth in a stateful failover system, use a shared directory that both the primary and back management platforms can access as a template pool, an iSCSI shared directory, FC shared directory, NFS, NVMe-oF shared directory, or shared file system for example. If no shared storage is available, create a local synchronization partition as a template pool. The primary management platform will automatically synchronize the data in the partition to the backup management platform.

Procedure

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Add Template Pool.

  5. Configure the parameters as described in "Parameters."

  6. Click OK.

Parameters

• Type: Select a storage type. Options are iSCSI Shared Directory, FC Shared Directory, Network File System, NVMe-oF Shared Directory, and Shared File System Directory. ARM hosts do not support NFS. Hosts that run the Tencent operating system do not support NVMe-oF shared directories. You can select the Local File Directory option only in a non stateful failover system. You can select the Local Synchronization Partition option only when the following requirements are met:

○ A stateful failover system has been set up.

○ The management platform hosts are not added to management platforms as CVK hosts.

○ No local synchronization partition has been created.

If you select the Local File Directory option, set the mount point of the local directory on the management platform host and the mount point must start with /vms/.

If you select the Local Synchronization Partition option, set the following parameters (not supported on ARM hosts):

○ Target Path: Enter the mount point of the template pool on the management platform host. It must start with /vms/.

○ Local Sync Partition: Only logical disks or partitions with the same name and capacity in both primary and backup management platform hosts can be used. Creating a local sync partition will format the disk or partition. You can create a maximum of one local sync partition. NVMe disks cannot be used as local sync partitions. As a best practice, set the size of a local synchronization partition to be not larger than 4 TB.

If you select the iSCSI Shared Directory option, set the following parameters:

○ Target Path: Enter the mount point of the template pool on the management platform host. It cannot start with /vms/ or /dev/ and cannot be /dev/.

○ IP Address: Enter the IP address of the iSCSI storage server. A single IP address indicates a single path and multiple IP addresses indicate multiple paths. To enter multiple IP addresses, use semicolons to separate them, for example, 192.168.0.27;192.168.10.27;2001🔤ef::90. In a stateful failover environment, both the primary and backup nodes must be reachable to the shared storage.

○ LUN: Select the LUN of the iSCSI shared directory. Make sure the selected LUN is not used by any shared file system, iSCSI network storage, template pool, or any other management platform management platform. In a stateful failover system, make sure the LUN is accessible to the primary and backup management platforms.

If you select the FC Shared Directory option, set the following parameters:

○ Target Path: Enter the mount point of the template pool on the management platform host. It cannot start with /vms/ or /dev/ and cannot be /dev/.

○ NAA: Select the NAA of the FC shared directory. Make sure the selected LUN is not used by any shared file system, FC network storage, template pool, or any other management platform management platform. In a stateful failover system, make sure the LUN is accessible to the primary and backup management platforms.

If you select the NVMe-oF Shared Directory option, set the following parameters:

○ Target Path: Enter the mount point of the template pool on the management platform host. It cannot start with /vms/ or /dev/ and cannot be /dev/.

○ IP Address: Enter the IP address of the NVMe-oF storage device. A single IP address indicates a single path and multiple IP addresses indicate multiple paths. To enter multiple IP addresses, use semicolons to separate them, for example, 192.168.0.27;192.168.10.27;2001🔤ef::90. In a stateful failover environment, both the primary and backup nodes must be reachable to the shared storage.

○ UUID: Unique identifier used to uniquely identify and locate specific storage devices in a virtualization system to ensure that the virtualization system can correctly identify and access the required storage resources.

If you select the Network File System option (not supported on ARM hosts), set the following parameters:

○ Target Path: Enter the mount point of the template pool on the management platform host. It cannot start with /vms/ or /dev/ and cannot be /dev/.

○ Source Host IP: Enter the IP address of the network file system. In a stateful failover system, make sure the primary and backup management platforms can reach the network file system.

○ Source Path: Enter the path of the network file system.

If you select the Shared File System Directory option, set the following parameters:

○ Target Path: Enter the mount point of the template pool on the management platform host. It must start with /vms/.

○ Shared Storage Pools: Select a shared file system. In a stateful failover system, the primary and backup management nodes must have been added to a cluster as service nodes and have the same shared file system mounted. In a single-node environment, a shared file system must have been added to the management platform.

○ Storage Name: Enter the name of the template pool folder.

Start a template pool

Enable an inactive template pool for the system to identify it. An active template pool can be used to store new VM templates or deploy VMs.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Start in the Actions column for a template pool.

  5. In the dialog box that opens, click OK.

Suspend a template pool

Perform thist task to suspend an active template pool for future use or for system maintenance.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Suspend in the Actions column for a template pool.

  5. In the dialog box that opens, click OK.

Delete a template pool

If a template pool is a local directory and contains VM templates, the template pool cannot be deleted.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Delete in the Actions column for a template pool.

  5. In the dialog box that opens, click OK.

Search VM templates

Perform this task to filter out the VM templates that are in a template pool but are not displayed in management platform. You can import these VM templates to management platform so they can be downloaded, distributed among template pools, or used to deploy VMs.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Search in the Actions column for a template pool.

  5. Select the target VM templates, and then click Import.

Expand a template pool

Only iSCSI, FC, and NVMe-oF storage resources support expansion.

When the existing template pool has insufficient space, perform this task to expand the template pool. This function enables flexible capacity expansion, ensuring that VM templates can be uploaded normally.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click Expand in the Actions column for a template pool.

  5. Specify the amount of capacity to be added, and then click OK.

Display information about a template pool

Perform this task to view the configuration information of existing template pools.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click Template Pool.

  4. Click View in the Actions column for a template pool.

Manage management platform storage adapters

In a stateful failover network, if the host that runs management platform is not added to the system as a CVK host, you can view information about the storage adapters used by the host, set the IQN, and perform a device scan through this feature. ARM hosts do not support this function.

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click a host.

    ○ To edit the IQN of an open-iSCSI or NVMe-oF storage adapter, click Edit in the Actions column for the adapter.

    ○ To perform a device scan, click Scan in the Actions column for a storage adapter.

Firewall settings​

A host firewall enables you to view the services used by a host and the port numbers for the services

and set the IP addresses that are allowed to access specific port numbers. It can effectively control network access and prevent unauthorized access and attacks to protect hosts. On the System > Stateful Failover > Firewall Configuration page, you can configure host firewall settings for the primary and backup nodes in a centralized manner.

Restrictions and guidelines

• If an IP address can access management platform through HTTPS, it can still access the VNC Web service even if it is not in the allowed IP address list for the VNC Web service.

• The firewall feature is not available for hosts that use software versions E073x and E076x.

• A host firewall only identifies and limits the incoming traffic of hosts.

• Deleting a host also deletes the firewall configuration for that host. After you change the IP address of a host from the XConsole of that host, you must restart that host to update the firewall configuration. If you fail to do so, the original allowed IP addresses will remain in the allowed IP address list for all ports.

• If a stateful failover system is deployed, you must make sure port 22 of the quorum node is reachable to the other nodes. The host firewall configuration in stateful failover management takes effect only on the primary and backup nodes and does not take effect on the quorum node.

• After a host is restored after stateful failover, you must click Synchronize in the firewall configuration in stateful failover management to synchronize the firewall configuration.

• To avoid affecting features running on the system, use the following table when you set the list of allowed IP addresses. Feature Description Recommended operations Make sure the quorum node is reachable Allow the relevant ports or to the primary and backup nodes. Setting disable the host firewall, and Stateful failover up a stateful failover system requires use then set up a stateful failover of ports 22, 20136, and 20138 of the system. primary and backup nodes. To interoperate with major cloud Major cloud products such as NCloud, or third-party Open all ports to IP addresses product or software such as AnyBackup of Aishu related to major cloud products third-party and Runstor, allow relevant IP addresses or third-party software. interoperation to access ports such as HTTP services. Port 8080 or 8443 is required when the Adding an external NSphere system or Usphere is added as Open ports 8080 and 8443. platform an external platform. When copying files from the Bare metal management host to a bare metal server, Open port 22. management the SCP service is required. Site disaster recovery requires use of Site disaster ports 8080 and 8443 for the protected Open ports 8080 and 8443. recovery site and the recovery site. Same as major cloud product or Same as major cloud product Anti-virus third-party interoperation. or third-party interoperation. Site incorporation and VM migration Open ports 8080, 8443, 22, Cloud rainbow require use of ports 8080, 8443, 22, 20199, and ports 49152 to 20199, and ports 49152 to 49215. 49215. Management Management platform data migration Open ports 8080, 8443, and platform data requires use of ports 8080, 8443, and 22. 22. migration Log backup requires use of port 22 on Log backup Open port 22. the destination. Data backup on a remote server in Data backup requires use of port 22 on Open port 22. backup the destination. management The management platform manages hosts and VMs on the hosts by calling Host management Open ports 26165 and 26167. ports 26165 and 26167 of the host management platform. The host scanning feature during cluster Scanning hosts creation requires the use of port 8081 of Open port 8081. the management platform.

Add a host firewall

  1. On the top navigation bar, click HA Service.

  2. From the navigation pane, select Stateful Failover.

  3. Click Firewall Configuration.

  4. Click Add. On the page that opens, configure the parameters. You can select or add one or multiple policies and set the access limit type.

    ○ Select Policy: Select an existing policy, or create a new policy and then select it. When you create a new policy, configure the following parameters:

    ▪ Name: Name of the host firewall policy.

    ▪ Direction: Traffic direction defined in the host firewall policy. Options are Inbound, Outbound, and Inbound, outbound. The inbound or outbound direction is determined with the local host as a reference.

    ▪ Description: Description of the host firewall policy.

    ▪ Protocol: Select the protocol that the host firewall policy uses to restrict traffic. You can select UDP, TCP, or TCP/UDP.

    ▪ Port: Port number of the host firewall policy. You can enter multiple ports and port groups.

    ○ Access Limit Type: Select an access limit type for the policy. By default, the inbound direction is restricted.

    ▪ Allow All: Ports associated with this policy allow the connections from all IP addresses.

    ▪ Internal Only: Ports associated with this policy allow only the connections between all hosts on the platform.

    ▪ Allowlist: Ports associated with this policy allow only the connections of all hosts (internal IPs) on the platform and the IP addresses in the allowlist.

    ▪ Denylist: Ports associated with this policy allow only the connections of all hosts (internal IPs) on the platform and the IP addresses not in the denylist.

  5. Click OK.

View firewall settings for a host

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click the Firewall Configuration button. All firewall policies for the current hosts are displayed.

Edit firewall settings for a host

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click the Firewall Configuration button.

  4. Click Edit in the Actions column for a service.

  5. Edit the access limit type as follows:

    ○ Allow All: Ports associated with this policy allow the connections from all IP addresses.

    ○ Internal Only: Ports associated with this policy allow only the connections between all hosts on the platform.

    ○ Allowlist: Ports associated with this policy allow only the connections of all hosts (internal IPs) on the platform and the IP addresses in the allowlist.

    ○ Denylist: Ports associated with this policy allow only the connections of all hosts (internal IPs) on the platform and the IP addresses not in the denylist.

  6. Click OK.

Synchronize firewall settings for a host

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Stateful Failover.

  3. Click the Firewall Configuration button. If firewall configuration must be synchronized, the Synchronize button will appear in the upper left corner of the pop-up window. Click this button to synchronize the firewall configuration.

Remove firewall settings for hosts

  1. On the top navigation bar, click HA Service.

  2. From the navigation pane, select Stateful Failover.

  3. Click Firewall Configuration.

  4. Select the target services, and click Remove. In the dialog box that opens, click OK.

Edit the priority of VMs in a protection group

Restrictions and guidelines

• The priority of a VM can be modified only when the site is operating correctly and the number of VMs is greater than 1.

• If you delete a VM when Editing its priority, management platform reloads the VM list.

Procedure

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Disaster Recovery Center > Protection Groups.

  3. Click a protection group. The VMs in the protection group will be displayed in the VMs Under Protection area.

  4. Click Edit Priority. Drag a VM up or down to Edit its priority. VMs with a higher priority will be recovered in the recovery site first.

  5. Click OK.

Edit the priority of a recovery plan

Perform this task to Edit the priority of a recovery plan.

Restrictions and guidelines

You can Edit the priority of a recovery plan only when the number of recovery plans is greater than 1.

Procedure

  1. On the top navigation bar, click HA Service.

  2. From the left navigation pane, select Disaster Recovery Center > Recovery Plans.

  3. Click Edit Priority, and then drag the name of the target recovery plan up or down to Edit the priority.

  4. Click OK.