Has any one ever used Double Take?

http://oldbbs.dlbaobei.com/qwer1234/index.php?q=aHR0cDovL3d3dy5kb3VibGV0YWtlLmNvbS9wcm 9kdWN0cy9kb3VibGUtdGFrZS9kZWZhdWx0LmFzcHg%3D

My concern is this ..

Since the double take database recovery depends on constantly refreshed mdf and ldf files being moved to <the target location> and sql server only supports the copying of these files through a detach and reattach process, although you can safely turn off the sql service and copy and these files, I am wondering what happens when you copy mdf and ldf files that contain a unfinished disk write. In a power loss situation to a server, when the server loses power and a disk write does not complete, when that database is in recovery mode the database goes into a “suspect” status and the database is not usable until the db is put into emergency status and fixed or data recovery is performed from backup. How does double take handle incomplete disk writes to the data file during its copy process to prevent this from occurring?

Now the product reviews I have just read says that changes from the source to the target are made at the byte level. So if a byte is changed, that byte is moved to your target server. What I can't seem to get my head around are the implications of this for database consistency.

Anyone have any light to shed for me?Sorry dude...what do you need to use a product like that for?|||We use it here. So far, it has worked out very well. The only problem we had was when the mirroring process had not finished, and someone tried to fire up the target database. If you have a power outage at your main site, you may lose a few transactions at the destination side, but it is a lot better than trying to get tapes assembled, in the drive, etc., etc..

We even test the system 3 or 4 times a year. In 3 years or so of doing it this way, I have yet to have a complaint from the OS admins who run my scripts to get the databases back online down there (What? You think they send me to do the recovery tests?).|||Not my idea and I am mad busy (no time to impliment sql replication) and we are doing that whole ASP thing and need to replicate data offsite to another data center, since this sql server in the other data center will not be running sql server until we need it, we save on licencing etc... lalalalalalala. My environment is totally crazy.|||how much does it cost?|||dunno. cheaper than a sql proc license. they just invite me to stuff to give sales people a hard time.