I'm implementing doubletake as we speak. I've found fail over and
replication work as advertised. If the fail back instructions are followed
explicitly fail back works fine as well
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rich Waldrop
Sr. Systems Engineer
Wausau Financial Systems, Inc
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: Gordon Olson [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 14, 2001 8:34 AM
To: NT System Admin Issues
Subject: RE: has anyone used doubletake successfully?
There is no problem with the failover it is the failback that does not work
as designed. You will be pretty much on your own also the tech support is
not very good. If you work with the product for more then a couple of days
you will not more then the support dudes.
We are using it with IIS, SQL7 running on NT and it works great, fails over
within 30 seconds. WE don't have a large volume of ecommerce so that is fine
for us. The fail back is the only spot where we have to go in and remove the
failed over ip manually because it just won't work right. It has once or
twice but most often it does not work as advertised. We have messed with it
and messed with it and - well, it is just easier to manually remove the ip
etc...
Hope that helps,
side note - we are using co-standby server for another app and it works
outstanding and it is much easier to configure. I like them both each are
unique.
-----Original Message-----
From: Heidi Pilewski [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 14, 2001 4:36 AM
To: NT System Admin Issues
Subject: Re: has anyone used doubletake successfully?
I'd like to know if you've ever had to failover to the other server and
how quickly and smoothly, if at all that went?
Also, did you look at any other products or solutions before deciding on
Double Take and, if so, why did you decide on Double Take?
I understand that my situation may differ but I'm looking at using a web
server (IIS) and SQL 7.0 on NT or 2000 as the operating system (depends
on when the decisions are made) and data will need to be replicated and
if the primary server goes down there should be as quick and smooth as
possible a transition to the "backup" machine. I've had personal
experience with NT Cluster server and, for this application, the
failover takes too long. We are hoping to minimize transaction loss as
much as possible.
Thanks,
Heidi Pilewski
Windows System Administrator
Software Engineering Institute
Carnegie Mellon
[EMAIL PROTECTED]
Ian Kelly wrote:
>
> Yes, and SQL 2000
> What do you need to know?
>
> Ian
> -------------------------------------------------------
>
> mailto:[EMAIL PROTECTED]
>
> -------------------------------------------------------
> The man who views the world at 50 the same as he did at 20 has wasted 30
> years of his life. - Muhammad Ali
>
> -----Original Message-----
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
