Step 1 - Enabling Redundant Mirroring Sessions on SQL Server
The first step in the process of configuring SQL Server redundant mirroring sessions is to enable redundant mirroring sessions.
Database Prerequisites
- 1 SQL Server 2014 or SQL Server 2016 – PRINCIPAL
- 1 SQL Server 2014 or SQL Server 2016 – Mirror
- 1 SQL Server 2014 or SQL Server 2016 – WITNESS
- The Principal, Mirror, and Witness SQL Server editions must be the same versions
- The database server names (Principal and Mirror) should be unique
- The database server names (Principal and Mirror) should be no more than 15 characters due to a SQL Server limitation
- SQL Management Studio needs to be installed on each server
- TCP/IP protocol needs to be installed and configured on each server
- Mixed mode needs to be installed and configured on each server
- Each SQL Server running as “LOCAL/SYSTEM”
- Access to write to files on file system
- Port 5022 and 1433 open on all three servers via Windows Firewall
-
The mirroring files are installed with the Spok Care Connect Suite installer and are located in the following locations:
-
Platform Server: <installdir>\Spok\Care Connect\Database\Mirroring\
-
AmcomCore
-
AmcomMeta
-
Common
-
-
Mobile server: <installdir>\Spok\Care Connect\Database\Mirroring\
-
AmcomAmcPremiseCore
-
-
- All of the Spok databases that need to be mirrored need to be installed on the Principal server. This can be done by running Spok Care Connect Server.msi and choosing to deploy the databases or running the scripts from the scripts folder manually.
- The SQL scripts are written to access the C: drive. Work with the customer to get permission to the C: drive or alter the scripts so they can access another drive.