SAN

Hi,
Planning to put a SANs in each of our data centers and have the D:\ and E:\
drives of a sql server replicating to the remote data center. HP guaranties
the proper replication of the drives with their asynchronous repliaction. I
will also have a server for disaster recover at the remote location with SQL
Server 2000 installed on it in case our main data center goes down. What
would be the most efficient way to bring the sql server up in a case of
disaster?
Thanks
--
--
Senior DBA
"I saw it work in a cartoon once so I am pretty sure I can do it."I'd be really careful with SQL Server working with asynchronous disk
replication. It may work out for you, but do test its behavior thoroughly. We
do synchronous disk replication. In that case, it is simply a matter of
ensuring the replicated volumes on the other side are visible to the host,
and start the SQL Server service. As far as SQL Server is concerned, it's the
same as the instance just stopped and restarted, and it would go through the
normal rollback roll forward process.
Linchi
"Sas" wrote:
> Hi,
> Planning to put a SANs in each of our data centers and have the D:\ and E:\
> drives of a sql server replicating to the remote data center. HP guaranties
> the proper replication of the drives with their asynchronous repliaction. I
> will also have a server for disaster recover at the remote location with SQL
> Server 2000 installed on it in case our main data center goes down. What
> would be the most efficient way to bring the sql server up in a case of
> disaster?
> Thanks
> --
> --
> Senior DBA
> "I saw it work in a cartoon once so I am pretty sure I can do it."|||I will definelely test the synch/asynch replication. I probably did not
explain what I want to do properly but here is some more info.:
1. Host A at location A uses a SAN. The C:\ drive is local to the server,
the D:\ and E:\ drives are on the SAN
2. Host B is location B and has a local C:\ drive.
3. Drive D:\ and E:\ on Host A at location A are being replicated to the SAN
at location B.
What I basically want to know is HOW Host B can take over if location A is
completely out? (note that C:\ drive is not being replicated). Please give as
much info. as possible or how you would implement this!
Thank you for your time
--
Senior DBA
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Linchi Shea" wrote:
> I'd be really careful with SQL Server working with asynchronous disk
> replication. It may work out for you, but do test its behavior thoroughly. We
> do synchronous disk replication. In that case, it is simply a matter of
> ensuring the replicated volumes on the other side are visible to the host,
> and start the SQL Server service. As far as SQL Server is concerned, it's the
> same as the instance just stopped and restarted, and it would go through the
> normal rollback roll forward process.
> Linchi
> "Sas" wrote:
> > Hi,
> >
> > Planning to put a SANs in each of our data centers and have the D:\ and E:\
> > drives of a sql server replicating to the remote data center. HP guaranties
> > the proper replication of the drives with their asynchronous repliaction. I
> > will also have a server for disaster recover at the remote location with SQL
> > Server 2000 installed on it in case our main data center goes down. What
> > would be the most efficient way to bring the sql server up in a case of
> > disaster?
> >
> > Thanks
> >
> > --
> > --
> > Senior DBA
> > "I saw it work in a cartoon once so I am pretty sure I can do it."