Bill Baer /bɛːr/

Conference season is upon us and it’s gearing up to be a great way to close out the year - join me at the 2009 Microsoft SharePoint Conference in Las Vegas at the Mandalay Bay Convention Center October 19th through October 22nd, 2009 or for those locally and can’t make the conference join me at the 2009 Pass Community Summit with Burzin Patel November 2nd through November 5th, 2009 at the Washington State Convention and Trade Center in Seattle.

I missed this one, but better late …. A new whitepaper has been released outlining configuring disaster recovery across SharePoint farms by using SQL Server log shipping – read more…

I was just reading Todd’s post on preparemove, and he does a good job of covering the changes in profile synchronization and related GUID reset/reassignment introduced by the application of the Infrastructure Update. There is one significant problem this change mitigates, specifically for those looking for a level of search redundancy through a dual-crawl architecture. In most scenarios where a dual-crawl architecture is implemented, an Office SharePoint Server Search instance in the primary datacenters crawls its localized content, and a separate, unique Office SharePoint Server Search instance in the secondary datacenter crawls the content in the primary datacenter.

I’ve discussed on several occasions Microsoft SQL Server 2005 Database Mirroring with Microsoft SharePoint Products and Technologies as a method by which database mirroring can provide intra-datacenter high-availability; however, am frequently asked how Microsoft SQL Server 2005 Database Mirroring can provide protection from datacenter failure. While possible, you generally do not want to geographically distribute your principal and mirror instances due to potential problems with maintaining synchronicity and bandwidth/latency constraints instead maintaining and intra-datacenter session to provide local fault tolerance; however, you can implement Microsoft SQL Server 2005 Log Shipping in conjunction with Microsoft SQL Server 2005 Database Mirroring to provide a standby copy of your databases in the remote datacenter.

As Microsoft SharePoint Products and Technologies becomes more business critical for organizations, data protection and redundancy become primary objectives in any size deployment. Disaster recovery and redundancy can be achieved using any of a collection of available technologies to include SQL Server 2005 Database Mirroring for redundancy and hardware or software-based replication solutions for disaster recovery or geographic replication. One of the most seamless methods available to a SharePoint deployment for geographic replication is SQL Server 2000/2005 Log Shipping.