This scenario is the primary case for active/passive clustering. In
clustering, both servers share the disk array, but only one server
'controls' the disks. The clustering service uses a heartbeat to monitor
the state of the primary server. In the event that node 1 fails, the
clustering service transfers control of the disk array to the other server,
and the database stays up.

I am not aware of any other way for 2 database servers to use the same
databases.

Kevin Martin
Database Engineer
Multimedia Games



-----Original Message-----
From: [Email Address Removed] [mailto:[Email Address Removed] Wednesday, May 21, 2003 9:42 AM
To: LazyDBA.com Discussion
Subject: Disaster Recovery w/EMC



Has anyone run across or composed a disaster recovery document for the
following scenario?

FACTS:
Our SQL Server 2000 databases are located on an EMC Disk Array.
The SQL Server software itself is loaded on the local disk.

SCENARIO:
Catastrophic local hardware failure on the production machine requiring
extended outage.
The need arises to swing the EMC disks to another machine and bring the
databases up so our apps can continue. Preferably with the same "instance"
name as the old production machine (for application dependancies).

Any help would be appreciated.

Thanks.





---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed] mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.481 / Virus Database: 277 - Release Date: 5/13/2003


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.481 / Virus Database: 277 - Release Date: 5/13/2003

MS Sql Server LazyDBA home page