Re: SQL Server High Availability/Fault Tolerance.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Fully agree with Russ, explore the SQL2005 native features for high
availablility

One more, which you should look at (other than log-shipping and database
mirroring) is Replication.
Each one of those technologies have pro's and con's, it is a matter of
comparing and choosing the one which fits your business requirement and
budget.

rgds,
Edwin.


"Russ Kaufmann (MVP)" <russ@xxxxxxxxxxxxxxx> wrote in message
news:OWRzpX4DHHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
"Sezgin" <anonymous@xxxxxxxxxxxxx> wrote in message
news:%23ttfOwtDHHA.3444@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

Currently we have the following setup:

2 Node Active/Passive SQL Server 2000 Enterprise Ed. Cluster,running on
Windows 2003 Enterprise Ed. Single production database,about 1.5 GB in
size,growing rate is about 150 MB per month.
The shared storage is on HP EVA 5000.The 2 servers and SAN are all in
the
same room.
Both hardware and software upgrade are planned for the near future. Key
points are High Availability and Fault Tolerance.
SQL Server 2005 Standard or Enterprise Edition is considered as the DB
software because large portion of the business logic is implemented in
complex Stored Procedures,making use of T-SQL.
After the upgrade 2 separate buildings will be used. At each location we
are planning to have 1 SAN and 2 SAN switches,servers, tape libraries
and
Ethernet switches. SAN and Ethernet switches in the 2 buildings will
have
connections between them,the distance is about 100 metres. Possible
choice
for SAN is the NetApp FAS 3050C model,which is advertised to have
software solutions for copying data between SAN's.
I am doing a research on the High Availability/Fault Tolerance/Disaster
Recovery solutions for the SQL Server database.
Is there any solution providing automatic Failover even in the event of
complete SAN failure(for exapmle in the event of fire or earthquake)
,assuming that we have 1 SQL Server and SAN in each buiding and 1 of the
buildings remains intact ?

With SQL, you can use Geo Clustering, as discussed by Edwin. For more
information refer to the following articles:
http://support.microsoft.com/default.aspx?scid=kb;en-us;280743

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/optimize/geoclust.mspx

http://www.microsoft.com/windowsserver2003/techinfo/overview/clustergeo.mspx

With SQL, you can also use log shipping to provide quick disaster
recovery.

With SQL 2005, you can now use Database Mirroring. For more info on
Database
Mirroring refer to these links:
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirfaq.mspx

http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

http://www.microsoft.com/technet/prodtechnol/sql/themes/high-availability.mspx

I think your best, least expense, least complicated, and easiest to
support
solution will probably be database mirroring. Your mileage may vary.


--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

The next ClusterHelp classes are:
Denver starting Nov 28th
NYC starting Dec 4th.









.

Relevant Pages

  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... I have had quite a number of clients that used a SAN for a database server and suffered significant performance problems because their underlying SAN infrastructure was a huge stripe across many drives. ... By application files I mean the binn folder which contains the sql server executable among other things. ...
    (microsoft.public.sqlserver.setup)
  • Re: Switch a Share Drive from shared SCSI to SAN
    ... Creating Databases or Changing Disk File Locations on a Shared Cluster ... Drive on Which SQL Server 2000 was not Originally Installed ... Senior Database Adminstrator ... I want to switch the SQL data drive to a SAN drive. ...
    (microsoft.public.sqlserver.clustering)
  • Re: moving data in a database to another file on a SAN
    ... http://www.support.microsoft.com/?id=314546 Moving DB's between Servers ... for SQL Server ... I seem to remember that there is a way to move data from the file that stores the data for a database to another file and then delete the original file. ... I thought that might work for moving the data to a SAN. ...
    (microsoft.public.sqlserver.server)
  • Re: How to Move SQL System Databases
    ... Assuming I've successfully copied the entire database SAN ... system and user database data files are located) from the ... SQL Server Databases ...
    (microsoft.public.sqlserver.server)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)