SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

" + title + "

" + title + " — Tue, 24 Apr 2007 09:42:58 GMT

PingBack from http://www.virtual-generations.com/2007/04/24/sharepoint-2007-link-dump-4-24-2007/

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Marcel Jeanneau — Wed, 25 Apr 2007 19:24:55 GMT

Hi William, I've testing SQL 2005 Mirroring with MOSS but it's not working for me. I have 4 VPCs there I'm trying this: 3 SQL SP1 (principal, mirror and witness) and a MOSS RTM box. I installed MOSS using 7 accounts (Install account, farm account, moss app pool account, ssp app pool account, ssp service account, search account and index account). Well I configured SQL Mirroring successfully, and failover works fine (I tested it pausing the sql principal server and after a while put it back online, and it assumed de mirror role). So SQL is fine. The problem is when I try to reconfigure MOSS to point to the new principal server. According to the whitepaper I do first:

stsadm.exe -o renameserver -oldservername SQLPRINCIPAL -newservername SQLMIRROR

and restart MOSS. It SHOULD let me get to the Central Administration site to continue with the process. Well I can't get to the site. When I open the central admin site it tells me "Can't connect to the configuration database". If I switch SQL roles back to innitial state and issue stsadm -o renameserver on the reverse direction I get my portal back online. But certainly I can't take advantage of SQL mirroring since I can't reconfigure MOSS to point to the new principal database, at least, as I told you, following the whitepaper.

Any idea?

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Bill Baer — Wed, 25 Apr 2007 19:40:49 GMT

In this scenario I would first use STSADM to set the database server for the SharePoint 3.0 Central Administration content database by running STSADM -o deletecontentdb (see example), assuming the operation completes successfully, run the STSADM operations required to instruct SharePoint Products and Technologies of the new configuration database server or new principal in this case. Once Central Administration is available from a web front-end computer, you can begin the process of updating the database server hosting the content databases, shared services, etc.

Example:

stsadm -o deletecontentdb -url "<http://centraladminwebapplicationurl>" -databasename "<centraladmincontentdatabase>" -databaseserver "<failedprincipal>"

stsadm -o addcontentdb -url "<http://centraladminwebapplication>" -databasename " <centraladmincontentdatabase>" -databaseserver "<newprincial>"

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Marcel Jeanneau — Wed, 25 Apr 2007 22:57:18 GMT

Additional question, when talking about Search Database Failover, what do you mean by <searchname>? Is it the search database name?

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Bill Baer — Thu, 26 Apr 2007 00:35:56 GMT

Search name refers to the name assigned to the search database; I should mention that while mirroring the configuration and other databases can be acheived through proper implementation of STSADM operations, support of database mirroring for SharePoint Products and Technologies is limited to the content databases.

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Last suggestion not working — Thu, 26 Apr 2007 23:10:18 GMT

William, I tried to remove the central admin content db from the failed principal with the command listed above, but it tells me "Farm not available. Reference to object not stablished as an object instance." The db name is right, dbserver name is right too. Any suggestion?

WSS FAQ additions and changes LII - 23rd - 29th April 2007

Mike Walsh's WSS and more — Sun, 29 Apr 2007 08:56:10 GMT

WSS FAQ additions and changes LII - 23rd - 29th April 2007

Mike Walsh's WSS and more — Sun, 29 Apr 2007 08:57:09 GMT

Fantastic Article on Using Database Mirroring with WSS 3.0/MOSS

Technical Weblog of Eric Charran — Thu, 03 May 2007 16:50:07 GMT

Bill Baer put together some fantastic guidance on how to consider database mirroring as a backup for

Replication and High Availability

Joel Oleson's SharePoint Land — Mon, 07 May 2007 09:51:51 GMT

The term replication comes up quite frequently in large deployments. It means a number of things to a

MOSS and SQL Mirroring - Advice from Technology Specialist

Tales From The Field — Mon, 07 May 2007 12:17:18 GMT

Bill Baer has started a series of blogs on the subject of SQL 2005 Mirroring as solution for failover

MOSS and SQL Mirroring - Advice from Technology Specialist

Tales From The Field — Mon, 07 May 2007 12:18:24 GMT

Bill Baer has started a series of blogs on the subject of SQL 2005 Mirroring as one solution for failover

SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 2 (Configuration)

William Baer — Sat, 26 May 2007 00:19:59 GMT

This is the second part of a multi-part series on using SQL Server 2005 Database Mirroring with SharePoint

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Pedro — Wed, 20 Jun 2007 10:00:39 GMT

Hi William, if I run this command:

stsadm –o editssp –title WSS_Serach_MyServer –ssplogin user –ssppassword something -searchdatabaseserver MyNewServer

I get the following error:

The following arguments are invalid: searchdatabaseserver

Can you explain whats wrong?

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Abi — Wed, 20 Jun 2007 17:21:51 GMT

Hi Bill Baer,

I am Abi and i aam learning database mirroring set up. Your article is very good and i learnt so many thing from your article. Also could you send me the article of clustering. I got lot of articles in clustering but what i am looking for has not yet been found.

I have the clustered Environment already set up. I need the documentation or artilcle that talks about managing the SQL server instances in the clustered environment. If you can, please send me the artilce or documents whatever you have to manage the SQL Server Instance in Clustered Environment.

I look forward to hearing from you soon.

Thank you.

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

gmagerr — Wed, 04 Jul 2007 16:00:15 GMT

Hi Bill

Great article. Well I have a medium farm set up with two SQL 2005 servers on the backend mirrored. I do the failover and run the stsadm commands to get all of my sites up and running. Everything works like a charm. The only thing that's not working is search. I run this command

stsadm -o editssp -title WSS_Portal_search -ssplogin contoso\spadmin -ssppassword p@ssw0rd -searchdatabaseserver sqlmirror

and I get an error message

The following arguments are invalid: searchdatabaseserver

stsadm -o editssp

-title <SSP name>

[-newtitle <new SSP name>]

[-sspadminsite <administration site url>]

[-ssplogin <username>]

[-ssppassword <password>]

[-indexserver <index server>]

[-indexlocation <index file path>]

[-setaccounts <process accounts (domain\username)>]

[-ssl <yes|no>]

Any ideas? I was on the phone with Microsoft for eight hours the other day. They couldn't help.

Thanks.

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Tate — Thu, 26 Jul 2007 01:37:16 GMT

Just got off the phone with MS and the stsadm -o edditssp with the searchdatabaseserver and sspdatabaseserver argumetns are invalid.

As Bill mentions (I did not catch this until I re-read this page) that mirroring is limited to the content databases only.

Mirroring, Log Shipping and High Availability resources

Noticias externas — Mon, 30 Jul 2007 04:42:54 GMT

Last week at TechReady I attended Mike Watson's and James Petrosky's talk on HA and DR scenarios

SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 3 (Failover)

Bill Baer — Thu, 02 Aug 2007 03:27:42 GMT

Database mirroring is increasing in popularity and becoming an integral part of high availability and

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

vipin — Tue, 14 Aug 2007 22:51:30 GMT

Hi,

Want to know s there any way on automatic failover i can fire stsadmin command to swith the Sharepoint to point to Mirrored DB, I tried to setup an job for Automatic Failover event alert of type CMD to run STSADMIN command.

But looks like its not taking affect.

Any clue how to verify that command is executing on alert or not some log or any thing else, because in job history I am see job execution time and duration which is same when Aautomatic failover event fired, when i change the DB status from 'ALTER DATABASE <<DB>> SET PARTNER FAILOVER;

Thanks

Vipin

Cluster or mirror?

Bill Baer — Thu, 16 Aug 2007 06:33:51 GMT

Should I cluster or mirror? A few short months ago, the answer to that question would have been easy,

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Bill Baer — Thu, 16 Aug 2007 07:34:32 GMT

I am assuming you are calling the renameserver operation?

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Muthu — Wed, 22 Aug 2007 16:29:12 GMT

Can somebody help "how to transfer WSS v3 database to another drive in same server instead of root drive"

I really need help on this...

muthu

re: SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 - Part 1 (Introduction, Overview, and basics)

Bill Baer — Thu, 30 Aug 2007 17:52:44 GMT

Muthu;

Default database locations are established on the SQL database server - these settings will define where new databases are created. For a list of sample T-SQL statements that can be used to move data and log files visit http://support.microsoft.com/kb/224071. If using SQL Server 2005 you can change the location using the Management Studio user inteface. To simply the data/log file move, you may wish to leave the database attached to Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007.

SQLTeach Vancouver Resources

Canadian IT Professionals — Tue, 27 Nov 2007 22:38:19 GMT

Database Mirroring Resources: SQL Server: Database Mirroring Best Practices and Performance Considerations

SharePoint Database Resources

Mirrored Blogs — Thu, 10 Jan 2008 00:11:28 GMT

Body: I just had a client ask about migrating a MOSS/WSS database and found this article and this one

Resources for TechNet Webcast: SharePoint Server 2007 (Part 3 of 6): Disaster Recovery

Full of I.T. — Wed, 23 Jan 2008 17:52:17 GMT

Here are some resources relating to part 3 of the SharePoint Server 2007 webcast series I'm presenting,

Database Mirroring Whitepaper Updated

Bill Baer — Mon, 03 Mar 2008 20:59:43 GMT

The SQL Server 2005 Database Mirroring with SharePoint Products and Technologies whitepaper has been

Setting up a mirrored failover environment for MOSS

ASPInsiders — Wed, 24 Sep 2008 10:30:16 GMT

I came across these great resources for setting up a mirrored failover environment for MOSS: SQL Server

Mirrored Failover Environment

Mirrored Blogs — Fri, 26 Sep 2008 09:44:01 GMT

Interesantes Recursos para configuración de entornos de Alta Disponibilidad para SharePoint en Base a

SharePoint Server 2007 SP 1 и SQL Server 2008

Вокруг BPIO: BI, SharePoint, Enterprise Search и т.д. — Tue, 31 Mar 2009 16:30:30 GMT

SharePoint SP1 и SQL Server 2008 вышли достаточно давно, однако я все же наблюдаю некоторую опаску при

MOSS 2007 and SQL Server 2008 - Better Together

Vantage Point - Bob German's WebLog — Wed, 08 Apr 2009 20:20:59 GMT

H1 { FONT-SIZE: medium } Many thanks to everyone who attended the MOSS 2007 and SQL 2008 "Better Together"

Office SharePoint Server 2007 and SQL Server 2008 - Better Together!

Microsoft Technology Centers blog — Thu, 16 Apr 2009 04:22:57 GMT

(Cross-posted from Vantage Point: Bob German's Weblog ) H1 { FONT-SIZE: medium } Recently Rich Crane