SQL Server prerequisites

When using an internal SQL Server instance, XProtect Management Server Failover replicates the contents of the SQL Server databases and triggers failover if the SQL Server instance fails.

For large VMS installations, you can connect the management server to an external SQL Server instance.

Internal SQL Server instance

The SQL Server installations must be identical on both nodes. To see a list of supported SQL Server editions for your VMS product, go to https://www.milestonesys.com/systemrequirements/.

Also, consider the following:

Prerequisite

Description
Database backup

Back up any existing databases to avoid loss of data.

During the failover cluster configuration, the wizard replicates the SQL Server databases on Node 1 to the SQL Server databases on Node 2. All data on the SQL Server databases on Node 2 is overwritten.
SQL Server service account

The SQL Server service must run under the same user account as the XProtect services.

To change a service account for the XProtect VMS, see Changing the service account that runs a VMS service
Database location

You can use the default or custom location for the VMS databases data and log files.

The default configuration is as follows:

  • The VMS databases data and log files are stored in the DATA folder.

  • The SQL Server error logs, trace log files, and log events are stored in the Log folder.

  • The DATA and Log folders belong to the same parent folder.

The default locations are:

  • C:\Program Files\Microsoft SQL Server\MSSQL{nn}.MSSQLSERVER\MSSQL\DATA

  • C:\Program Files\Microsoft SQL Server\MSSQL{nn}.MSSQLSERVER\MSSQL\Log

{nn} is the version number.

If you use custom locations for the data and log files, you can select them during the configuration of the failover cluster.
Virus scanning exclusions In your antivirus program, exclude the locations of the DATA and Log folders from virus scanning.
Instance name Verify that the instance name of your SQL Server is MSSQLSERVER. See View the SQL Server instance name.

External SQL Server instance

You can use a SQL Server instance that is hosted elsewhere in your network. XProtect Management Server Failover does not monitor the SQL Server databases when the SQL Server instance is hosted on a separate server.

The failover server configuration with external SQL Server does not work in a workgroup environment.

Prerequisite

Description
Permissions for the SQL Server user

In Microsoft SQL Server Management Studio, add a Windows user to the public role and map the user to the  db_owner database role for the following databases:

  • Surveillance

  • Surveillance_IDP

  • Surveillance_IM

  • LogserverV2

Connection

Verify that the VMS installations on both nodes:

  • Are connected to the external SQL Server instance.

  • The VideoOS IIS application pools on Node 1 are running.

  • The VMS services on Node 1 are running.
Service account

Make sure that the Management Server service on both nodes runs under the Windows user you added on the SQL Server computer.

If your SQL Server runs under a different user, you can change the account that runs the Management Server service. See Changing the service account that runs a VMS service.
Database conflicts

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: