Replication Tools for DR

[Kiwiinnz]

We are looking for Physical for Virtual replication tools at the application level, this is for our DR environment.

We are interest in products that will allow us to P2V and then conduct differential updates to keep them in sync we have already looked Leostream and Plate Spin, which seem to be the only products capable of this , does anyone know of any other ?

Any help appreciated

 

[ArizonaGeek]

We've been testing Double Take software. In fact the VM guys I have been dealing with recommended it even after we had already started our testing. So far it is doing everything it claims and then some.

You can do P2V, V2P, V2V, P2P... all pretty easily.

Cheers
Rob

The answer is always "PEBKAC!

 

[Kiwiinnz]

Thanks for the response Rob

I will take a peek at double take, what a hassle to get an evaluation copy.

It seems more geared toward Data Base replication, we use a tool called WanSync for this.

We are looking for a tool that will virtualise our Application servers (most have 3rd party software installed) after the initial VM is created we want to keep them in Sync with regular updates

Can you tell me if Double Take has this ability

Thanks again

 

[ArizonaGeek]

Although it seems like it is geared towards DB's it can be used for anything. They are like most higher end software companies, they want you to talk to a sales rep to get an evaluation. But there is so much to it and so many things you can do it actually worked out pretty good for us talking with them. We had them do a demo for us and they have been very helpful (more so than I figured they would since we haven't committed to buying anything yet) in answering any of my questions during my test. We are creating our DR now and implementing after the first of the year and have been pretty impressed with Double Take.

During our test, we've been able to fail over production servers across our lan in as little as 10 minutes and according to them, we should be able to do it across a WAN only a few minutes more than that.

To be fair I also tested Symantec Back Up Exec System Recovery and I hated it so much that if I never see another Symantec product again it would be too soon. Ok, it wasnt JUST the System Recovery software but that was added on to the pile of my dislike for them.

Cheers
Rob

The answer is always "PEBKAC!

 

[ArizonaGeek]

Also, I forgot to mention, that we use several in house built software that was coded in 1999. It wont even run on Server 2003, and we were able to fail over with no issues. The only requirements Double Take had was you had to fail over to like OS. Win 2000 to Win 2000 and Win 2003 to Win 2003 (32 bit had to go to 32 bit, but we could go 32 bit Enterprise to 32 bit Standard with no prob) but hardware was no issue. We did Dell to HP and back with no issues.

Cheers
Rob

The answer is always "PEBKAC!

 

[Arisap]

Just a note: DoubleTake's product can replicate and synch vmdk files. The only issue is that they snapshot the vmdk, transfer the -flat.vmdk file, apply the snapshot to the vmdk file and then snap it again, thereby leaving the vmdk in perpetual snapshot mode. Which is a performance hit. It also makes it impossible to take manual snapshots of any kind.

Just something to think about.

 

[Kiwiinnz]

Thanks for the info folks, if there are any other shorts falls you are aware of with double take or any other tools used please let me know

 

[ArizonaGeek]

See, we are using Symantec Backup Exec to pick up our vmdk files to tape and not replicating full servers across a WAN (imagine doing a 100+ gig vmdk file across a wan!!!) You are better off replicating Windows and important files as opposed to full server replication. Our plan is to build the server on site, do the full replication with Double Take on our LAN then move the server to an off site data center then only replicate changes across the WAN.

If you are moving full vmdk files, you are doing A LOT more work than you need to be doing.

Cheers
Rob

The answer is always "PEBKAC!

 

[Kiwiinnz]

We do the same here (build local then deploy to DR)and setup delta updates. (but using WanSync which seems to be Double Takes poor cousin).

Our setup is Physical Prod servers and VM's in our DR site we looked at backuping the VMDK's in DR, but agreed it was probably a waste of resource becuase we had the original server, its tape backup and another copy in DR.

I guess from the business aspect, it was not seen as economical to invest in addition resource, to cover an event where both the Prod and DR servers failed simulaneously.