Remote server

Here is a scenario what i want to do:
I have SQL 2000 server on windows 2000 server in two
different locations. I want to setup the local server to
copy the data to the remote server every 30 minutes or
so. In case the local server is down, i want to redirect
users to the other database server. Which way to go
either log shipping or replication? or any othere
suggestion? maybe third party tools.
Thank you.>--Original Message--
>Here is a scenario what i want to do:
>I have SQL 2000 server on windows 2000 server in two
>different locations. I want to setup the local server
to
>copy the data to the remote server every 30 minutes or
>so. In case the local server is down, i want to redirect
>users to the other database server. Which way to go
>either log shipping or replication? or any othere
>suggestion? maybe third party tools.
>Thank you.
1. You can use Double-Take for real-time replication and
failover reasons (when first server is down the
second "take" the ip address and is coming up).
2. Log shipping + scripts. Script must detect if first
server is down and change the ip address of the second
server
Cezar|||I'd be extremely careful with automatically switching the clients to the
warm standby server maintained via log shipping. Unless you carefully wire a
lot of automated and robust checks to ensure that all conditions are in
place as you have agreed with the business, it's too dangerous to let it
happen automatically.
I myself have never recommended or allowed any automatic switch to a warm
standby server. Nor have I heard anybody doing it in a serious production
environment. (I have a feeling that I might just hear from somebody here :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"cezar" <cezar_gheorghe@.hotmail.com> wrote in message
news:0a6601c3817b$e0338860$a401280a@.phx.gbl...
> >--Original Message--
> >Here is a scenario what i want to do:
> >
> >I have SQL 2000 server on windows 2000 server in two
> >different locations. I want to setup the local server
> to
> >copy the data to the remote server every 30 minutes or
> >so. In case the local server is down, i want to redirect
> >users to the other database server. Which way to go
> >either log shipping or replication? or any othere
> >suggestion? maybe third party tools.
> >
> >Thank you.
> 1. You can use Double-Take for real-time replication and
> failover reasons (when first server is down the
> second "take" the ip address and is coming up).
> 2. Log shipping + scripts. Script must detect if first
> server is down and change the ip address of the second
> server
> Cezar