Implementing Hardware Mirroring on SS2005 1

[JohnBates]

hi experts,

(I tried to post this earlier. If I have cross-posted, it was not intentional).

We will be moving to some kind of hardware mirroring technology (not SQL Server's mirroring) soon. This will mirror all files, database and Windows to the alternate server.

On the alternate server, should the SQL Server 2005 services be started? if yes, what state should the databases be - attached but not online? Not interested in having automatic failover.

Has anyone done this>?
Thanks, John

 

[mrdenny]

The SQL Server services should be stopped. When you want to fail over to the server simple start the service and it'll pickup the databases and roll forward any pending transactions.

You may find that the database mirroring of SQL Server 2005 has a lighter network load than disk mirroring via DoubleTake (or what ever product you are using).

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog

 

[JohnBates]

Thanks denny.

I'm actually using SQL Server's mirroring on this server now and it has worked reliably for a year.

But ideally we would mirror everything and have a better chance of the applications becoming available sooner after we failover. We will be testing the non-SQL Server mirroring in a couple months, don't know the name of the product yet.

So if all I need to do is have the SQL services stopped that is great.

Thanks, John

 

[mrdenny]

Yep, that should be all that needs to be done.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2008 Implementation and Maintenance / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Admin (SQL 2005/2008) / Database Dev (SQL 2005)

My Blog