"DoubleTake" competitiors
-
We are a Windows shop and are considering Doubletake software as part of our Disaster recovery efforts. Do you of any competing products?
TIA,
Barkingdog
-
CA XOSoft. They have a product (WANSyncHA SQL) that provides server (DB) wide DR solution.
-
Legato Octopus, but I believe that is now sold by EMC2 as RepliStor.
http://software.emc.com/products/software_az/replistor.htm?hlnav=T
-
Another voice for XOSoft, if it suits your needs. We have a very very warm spare 25 miles away, always ready with the same databases (including master). Dynamic DNS update handles failover - you choose automatic or manual. SQL Server db files are done by block, with write order and transactional integrity preserved. If you license for SQL Server, you can run the File sync as well for no extra charge - I use it to keep the backup files synced and some out of band config files.
It also knows when new databases or database files are added - as long as they are on the same disk. Add a disk and you will need to update the scenario.
Unlike some of the other things, it has no connection to how the apps are programmed.
Assured Recovery is an option that lets you bring the spare online for testing without having to do a resync when done.
And they have an Exchange aware product, it's why I knew about it at all. The company was bought out by CA - unfortunate because the original company was great to deal with. The product itself has not suffered, however, just the process of buying, supporting, etc.
Roger L Reid
-
So what about Mirroring in 2005. I have tried some of the 3rd party solutions and did not really care for them, but have had a mirrored server up for about 5 months now with no problems. I even cheat and do a snapshot off of the mirror for reporting purposes.
John.
-
Well I think it depends on what you want to do and how your SLA is written.
If you are interested in only user databases then SQL 2005 mirroring is a good and economical solution but the automatic failover part is dependent on the database connection type.
Double-take and perhaps the other "mirroring" products operate below the OS but above the device driver (where the virus checkers live) map block level changes and have network compression capabilities. In addition they have the ability to provide geographical DR for a number of applications besides databases.
We selected double-take since we support a number of RDBMS servers other than SQL Server. I like the HA monitoring, command scripting, and the ability to support virtual servers however I am sure the competitors have similar capabilities.
Lowell
-
Several years ago we had a lengthy discussion here about Double-Take...good and bad so make sure to read through it as there are some data integrity issues.
http://qa.sqlservercentral.com/forums/shwmessage.aspx?forumid=263&messageid=317781
We used Double-Take for several years and did not trust it. It mirrored very well (but we were worried about failover during a transaction or it mirroring a corrupted database.) but we never trusted the failover capability as we always had problems with it. We also had problems mirroring over a one of our slower WANs and also had issues with it crashing our server a couple of times (dblHook errors).
We currently use Polyserve for local failover and use log shipping for our disaster recovery site.
-
Take a look at NeverFail
-
Around here we refer to NeverFail as 'NeverWork' or 'AlwaysFail'; we ran the Exchange version for a while and it never worked.
Eddie Wuerch
MCM: SQL
Accepting all invitesViewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply