Small Highly Available Deployment

This topology moves us to Lync 2013 Enterprise Edition. This means you can scale to a higher number of users, and get true high-availability. You now require a load balancer for both Lync Web Services and Office Web Apps. With Lync Enterprise Edition and Backend SQL Mirroring, you can lose a host and have high-availability for user services with no administrative intervention. With Lync Server 2010 this topology would have required shared storage due to SQL clustering. With SQL Mirroring in Lync Server 2013, this deployment can work with direct attached storage.

DMZ Hosts 1 and 2 can be physically placed in the DMZ. The Lync Edge Servers can be polled and TMG Servers paired to provide high-availability in the event of a DMZ host failure, as shown in Figure 29.6.

Image

Figure 29.6. Small highly available deployment.

There is a fine line between this topology and the dual Standard Edition topology. The Enterprise Edition topology incurs the extra SQL and hardware costs, but is potentially scalable simply with the addition of more Front End Servers.

Tip

It is recommended to have three Front End Servers in a pool in Lync Server 2013, so ideally one of the two hosts would be specified to have two Front End Servers. However, if you lose the host with two Front End Servers, the third server will stop its services due to quorum loss. In this scenario you can use two Front End servers per physical host and the active SQL node will provide the final quorum vote.

Host Servers 1 and 2 Configuration:

• Windows Server 2012 with Hyper-V

• Dual 2.26GHz or higher CPU with 20 cores

• 96GB RAM

• 500GB SAS 10K disks with 16 spindles

• Eight 1Gb network adapters or multiple teamed 10Gb network adapters

Host Servers 1 and 2, Guest Configuration:

Lync Server 2013 Enterprise Edition:

• Six CPU cores

• 32GB RAM

• Dedicated 1GB network adapter or equivalent allocated network bandwidth

Microsoft SQL Server 2012:

• Six CPU cores

• 32GB RAM

• Dedicated 1GB network adapter or equivalent allocated network bandwidth

Office Web Apps Server 2013:

• Four CPU cores

• 12GB RAM

• Dedicated 1GB network adapter equivalent allocated network bandwidth

Host Server 3 Configuration:

• Windows Server 2012 with Hyper-V

• Dual 2.26GHz or higher CPU with 8 cores

• 48GB RAM

• 500GB SAS 10K disks with 8 spindles

• Four 1Gb network adapters or multiple teamed 10Gb network adapters

Host Server 3, Guest Configuration:

Lync Server 2013 Enterprise Edition:

• Six CPU cores

• 32GB RAM

• Dedicated 1GB network adapter or equivalent allocated network bandwidth

Microsoft SQL Server 2012 Witness Server:

• Two CPU cores

• 4GB RAM

• Dedicated 1GB network adapter or equivalent allocated network bandwidth

DMZ Host 1 and 2 configuration:

• Windows Server 2012 with Hyper-V

• 2.26GHz or higher CPU with eight cores

• 32GB RAM

• 500GB SAS 10K disks with eight spindles

• Four network adapters

DMZ Host 1 and 2, Guest Configuration:

Lync Server 2013 Edge:

• Four CPU cores

• 16GB RAM

• Two dedicated 1GB network adapters

Forefront TMG Reverse Proxy:

• Four CPU cores

• 8GB RAM

• Dedicated 1GB network adapter

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset