Welcome to MSDN Blogs Sign in | Join | Help

Configuring Database Mirroring for SharePoint Products & Technologies

Check out this new white paper which details how to configure Database Mirroring in SQL 2005 for SharePoint Server and WSS 3.0. (Includes T-SQL Commands)

Using Database Mirroring with Office SharePoint Server and Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkId=83725&clcid=0x409) 

Table of Contents


Introduction to Database Mirroring

  • Database Mirroring Modes
  • Security Associated with Database Mirroring

How to Set Up Database Mirroring with SharePoint Products and Technologies

  • Prerequisites
  • Recommended Topologies
  • Recommend Database Limits
  • Performance and Scale
  • Setup Steps
  • Database Mirroring with Certifcates and Full Recovery
  • Setting  up a Witness Server

Recovering from a Failure

  • Types of Failover
  • Automatic Failover
  • Manual Failover
  • Forced Failover (possible data loss)
  • Notifying SharePoint Products and Technologies when a Failover Occurs
  • Configuration Database and Administration Content Database
  • Content Database
  • Search Database
  • Shared Service Provider Database (Office SharePoint Server only)
Published Tuesday, March 06, 2007 12:24 AM by joelo
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Configuring Database Mirroring for SharePoint Products & Technologies » Enterprise 2.0 and web 2.0 resources

PingBack from http://www.virtual-generations.com/2007/03/06/configuring-database-mirroring-for-sharepoint-products-technologies/

Tuesday, March 06, 2007 1:50 AM by Configuring Database Mirroring for SharePoint Products & Technologies » Enterprise 2.0 and web 2.0 resources

# SQL Server 2005 Mirroring con MOSS: Mi experiencia

Hace unos días prometí un curso de personalización de MOSS. Lamentablemente me veo imposibilitado de

Tuesday, March 13, 2007 2:01 AM by Piensa SharePoint

# re: Configuring Database Mirroring for SharePoint Products & Technologies

I am trying to work through a test on database mirroring, but when i failover the config database and admin content database it doesnt appear to work. I execute the following commands after both are failed over

----

stsadm.exe -o renameserver -oldservername <OldPrincipalServer> -newservername <NewPrincipalServer>

iisreset

----

It doesnt work it get the following error.

Unable to connect to database.  Check database connection information and make sure the database server is running.

When i bring the admin content databse back to the original principle the admin site works great.

What am I missing?

Tuesday, May 08, 2007 12:19 PM by Scott

# re: Configuring Database Mirroring for SharePoint Products & Technologies

I have read in MSDN forums that MSFT officially does not support mirroring MOSS databases.  Any word on if this is accurate?

Friday, May 11, 2007 4:24 PM by Eric

# re: Configuring Database Mirroring for SharePoint Products & Technologies

>>I have read in MSDN forums that MSFT officially does not support mirroring MOSS databases.  Any word on if this is accurate?

Got a link?  I would also like to know if db mirroring is officially supported or not. We are looking for failovers solutions for our new sharepoint installation.

Thursday, May 24, 2007 10:19 AM by Jay

# re: Configuring Database Mirroring for SharePoint Products & Technologies

This was just what I was looking for. I have so many questions.  The Doc Says that this will work for SharePoint Services 3.0 is this confirmed.  Is it possible to perform steps in SQL Management Studio?  

I am having trouble understanding why Microsoft would create such a cool feature "DB Mirroring" that doesn't work well with any of their Applications. i.e. CRM, SharePoint, etc... which databases did they think we wanted to make Highly Available.  

Monday, June 04, 2007 10:06 PM by Mersild

# re: Configuring Database Mirroring for SharePoint Products & Technologies

i am trying to configure database mirroring with a witness for automatic failover.

The problem is that all the WMI events can only be run on the principal when the failover occurs. if the principal shutdowns and then we failover, the WMI event is not generated and i cannot issue  the command to change the server or the content dataabses. is there any way to know on the witness when a failover occurs.

Friday, July 06, 2007 2:34 AM by Udit Ghai

# re: Configuring Database Mirroring for SharePoint Products & Technologies

I wrote a script to switch automatically all SharePoint databases from the Proncipal SQL Server to the Mirrored SQL Server, if the Principal SQL Server fails.

http://chandlersblog.at.im/

Regards,

Chris

Saturday, January 05, 2008 11:31 AM by Chris

# Day 2: Support links and Q&A

Today we covered capacity planning, high availability, server roles and migration.&#160; Here are a list

Tuesday, April 15, 2008 11:35 PM by Spic and Spam

# re: Configuring Database Mirroring for SharePoint Products & Technologies

I am confused about the steps I would need to take to get my 'mirrored' MOSS farm up and running.

I am planning on having 2 farms in geographically different locations, one for production, one for disaster recovery, with content databases mirrored between the two locations. I was planing on having the second farm configured with WFE, index servers, etc. at the disaster recovery site, basically the configuration database and my web application already configured pointing to a simple content database. After switching my disaster recovery database to be 'primary', what would I need to do?

Since I already have a farm and a web application configured can I simply attach my content databases. I would not need to run "renameserver" since I am my Farm already knows about my DR SQL server that now has my primary content dbs. I am confused on what steps I need to take to get up and running.

Wednesday, June 25, 2008 12:39 PM by thomasonk

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker