Skip to main content
Click here if you are having trouble viewing this site
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Resources
Spok

Step 3 - Enabling Redundant Mirroring Sessions on SQL Server

  1. Last updated
  2. Save as PDF
This step is optional. You can enable Redundant Mirroring Sessions on the SQL Server.

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 on which the encryption databases will need to be restored.

  1. Identify the three database servers shown below. If you do not know the name of your server, reference Microsoft’s documentation for information on obtaining the server name.
    • 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. Note the fully qualified domain name (FQDN) for each of the three servers.

  5. Create entries in the C:\windows\system32\drivers\etc\hosts file for each server, as shown below.

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

You must enter the actual hostname and DNS domain/suffix for each server. You cannot create placeholder hostnames in the hosts file.