October 31, 2007 at 6:08 am
Is anyone attempting or has anyone successfully deployed MOSS2007 with a SQL 2005 Database Mirror on the backend? We are doing it in our lab with the automatic failover (principal, mirror & witness) and the SQL portion works great. The only issue is we have is that we have to manually switch MOSS over (via Sharepoint 3.0 Central Admin or stsadm) to the new content database on the other server. Thank you
October 31, 2007 at 8:00 am
This white paper which details how to configure Database Mirroring in SQL 2005 for SPS and WSS 3.0 - http://go.microsoft.com/fwlink/?LinkId=83725&clcid=0x409. Might help 🙂
Tommy
Follow @sqlscribeOctober 31, 2007 at 8:28 am
This is part of what we used to set up the DB Mirroring. Is the certificate something we have to set up in order to automatically repoint the content dbs? We've tested the automatic failover for SQL successfully but have to repoint to the other content db via stsadm or through the Central Admin console
October 31, 2007 at 8:36 am
Which isn't very automatic at all. :hehe:
October 31, 2007 at 10:06 am
yep... auto for SQL but not MOSS. gotta love it. we are tinkering with it sending alerts to my phone or email so I can then remote in and manual switch MOSS. again, not very auto..:pinch:
October 31, 2007 at 10:45 am
My co-hort in crime here provided me with a link that shows others have the same issue..
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1495973&SiteID=1:D
November 6, 2007 at 7:27 am
Bump. Just in case anyone didn't see this... still searching for a way to work it.
January 21, 2008 at 6:37 am
Hi all,
I've been working with db mirroring for some time. I've got it up and running in our production environment. I've written a batch file that automates all of the failing over to the mirror server and vice versa. Here's a link to the script. I've tested this extensively and it works great for me. Enjoy.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply