With Microsoft making increasing inroads with their Office Communications Server 2007 R2 platform, many integrators, VARs, and end-user customers are looking to find out more information on bringing the famed "five nines" (99.999%) of reliability to OCS 2007 R2.
Well, Microsoft has just released a white paper detailing how to ensure high reliability. According to Microsoft:
Using backup and restoration procedures for site disaster recovery as described in the Microsoft Office Communications Server 2007 R2 documentation library topic Backup and Restoration, can entail some downtime for users."
This white paper describes a site resiliency solution for Office Communications Server 2007 R2. The solution includes an Enterprise pool that spans two geographically separate sites. The solution provides a failover mechanism between the two sites to ensure that Office Communications Server functionality such as instant messaging, presence, and conferencing remains available even if one of the sites becomes unavailable.
This white paper is divided into three main sections:
* The Solution section provides an overview of the tested and supported site resiliency solution described in this paper.
* The Test Methodology section describes the testing topology, expected behavior, and test results.
* The Findings and Recommendations section provides practical guidance for deploying your own failover solution.
To successfully follow this paper, you should have a thorough understanding of Office Communications Server 2007 R2 and Windows Server 2008 Failover Clustering.
Good stuff!
Now you have no excuses to tell users when OCS 2007 goes down -- when really you stuck a second DHCP server on the LAN by accident or you disconnected the uplink cable when doing some cable rearrangement or you turned on an old PC that shared the same static IP address as the OCS 2007 server. Not that I've ever done anything like that and blamed Microsoft for the outage. Nope, not me!
White Paper Download
Well, Microsoft has just released a white paper detailing how to ensure high reliability. According to Microsoft:
Using backup and restoration procedures for site disaster recovery as described in the Microsoft Office Communications Server 2007 R2 documentation library topic Backup and Restoration, can entail some downtime for users."
This white paper describes a site resiliency solution for Office Communications Server 2007 R2. The solution includes an Enterprise pool that spans two geographically separate sites. The solution provides a failover mechanism between the two sites to ensure that Office Communications Server functionality such as instant messaging, presence, and conferencing remains available even if one of the sites becomes unavailable.
This white paper is divided into three main sections:
* The Solution section provides an overview of the tested and supported site resiliency solution described in this paper.
* The Test Methodology section describes the testing topology, expected behavior, and test results.
* The Findings and Recommendations section provides practical guidance for deploying your own failover solution.
To successfully follow this paper, you should have a thorough understanding of Office Communications Server 2007 R2 and Windows Server 2008 Failover Clustering.
Good stuff!
Now you have no excuses to tell users when OCS 2007 goes down -- when really you stuck a second DHCP server on the LAN by accident or you disconnected the uplink cable when doing some cable rearrangement or you turned on an old PC that shared the same static IP address as the OCS 2007 server. Not that I've ever done anything like that and blamed Microsoft for the outage. Nope, not me!
White Paper Download
Technorati
Del.icio.us
Slashdot
Digg
twitter
Look at the prerequisites (stretched vlan, sql 2008, synchronous replication, etc) you need some expensive stuff to get this working. Your statement "there is no reason to say OCS is down" is ok, but can it be implemented for real between two datacenters and an longer distance.