Configuring SQL Server Mirroring During Pool Creation in Topology Builder

Follow the steps below to configure SQL Server Mirroring when deploying a Lync Server Pool.

1. With Topology Builder open, and as part of the pool creation process, on the Define the SQL Store page click New next to the SQL Store box.

2. On the Define New SQL Server Store page, specify the primary SQL Server Store and select This SQL Instance Is in Mirroring Relation. Then, specify the SQL mirroring port number (the default is 5022), and click OK. See Figure 15.5 for an example of this configuration in Topology Builder.

Figure 15.5. Defining a new SQL Server Store.

3. Back on the Define the SQL Store page, select Enable SQL Store Mirroring and select New to define a new SQL Server.

4. On the Define New SQL Server Store page, specify the secondary SQL Server Store and select This SQL Instance Is in Mirroring Relation. Then, specify the SQL mirroring port number (the default is 5022), and click OK.

5. If you want to enable automatic failover, a witness is required. To define a witness, select Use SQL Server Mirroring Witness to Enable Automatic Failover, and then either select New to define a new SQL Server or select an existing server from the drop-down list.

6. On the Define New SQL Server Store page, specify the witness SQL Server Store and define a witness port number (the default is 7022). Figure 15.6 provides an overview of how this configuration would look in Topology Builder.

Figure 15.6. Results of defining a SQL mirror with automatic witness failover.

7. Complete the rest of the Pool Configuration Wizard in the Topology Builder.

8. Use Topology Builder to publish the topology. When you are publishing the topology, you will see an option to create both the primary and the mirror SQL databases.

9. Click Settings. You must define a path to use as the file share for the mirroring backup. This is used only when creating the initial mirror to copy files between SQL Servers.

10. Click OK and then Next. This process creates the databases and publishes the topology. This process also configures all SQL mirroring configurations. Any errors are reported in the final report.