Step I: Start the configuration on Node 2

After you have checked the prerequisites and prepared your system, you can start with the configuration of the failover cluster without data replication.

If you have two or more running management servers that are connected to the same SQL Server databases, your data might be corrupted.

To avoid potential database conflicts, before you start the configuration, go to Node 1 and:

Stop all VMS services. You can start the services after you have configured the failover cluster. See Start or stop a VMS service.
Stop all Internet Information Services (IIS) application pools for the VMS. You can start the application pools after you have configured the failover cluster. See Start or stop an Internet Information Services (IIS) application pool.

On Node 2:

In the notification area, right-click the Management Server Manager tray icon and select Configure failover management server.
Select Configure the secondary computer.
Make sure that you have installed the required system components and scheduled downtime.
On the Select connection protocol page, select a protocol for communication with the failover web console:
- To use a system-generared certificate, select HTTPS to secure your connection. During configuration, the wizard takes the first DNS entry from your DNS servers list to generate the certificate. If the DNS server is down, the failover cluster configuration might fail.
- If you want to use a custom certificate for encryption or you do not want to encrypt your connection, select HTTP.
On the Set a password for authentication page, specify a password for login to the failover web console. You need to set the same password on Node 1.

The wizard prepares the node and informs when successfully completed.

(For HTTPS only) Save the security code. To establish a secure connection between the nodes, you must specify the security code on the Node 1.

You are now ready to continue on Node 1. See Step II: Continue the configuration on Node 1.

XProtect Management Server Failover

Step I: Start the configuration on Node 2

Search results