Skip to main content
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Spok

Step 3 - Enabling Redundant Mirroring Sessions on SQL Server

This topic contains steps for part of the process for configuring SQL Server Redundant Mirroring Sessions as an optional configuration in Spok Mobile.

The database encryption uses a certificate and a private key that is generated on the SQL Server when the databases are installed. This certificate and private key need to be created on any other server in which the encryption databases are to be restored on.

  1. Identify three database servers:
    • PrincipalDB (Primary) server
    • MirrorDB (Mirror) server
    • WitnessDB (Witness) Server
  2. Note the servers’ IP addresses.

  3. Copy the mirroring SQL files from this installation package to each of the three servers.

  4. Gather the TRUE Fully Qualified Domain Name (FQDN) for the three servers.

  5. Create entries in the C:\windows\system32\drivers\etc\hosts file.

NOTE: The hostname you use for this is required for SQL Server. You cannot create three “fake” host names in the hosts file – it does not function without using the true System Name and DNS domain/suffix of the server.

For example:

192.168.1.1 principal.amcomsoft.com principal
192.168.1.2 mirror.amcomsoft.com.mirror
192.168.1.3 witness.amcomsoft.com witness

NOTE: If you do not know the name of your server, reference Microsoft’s documentation for information on obtaining the server name.