Feature |
VizionCore vReplicator |
Veeam Backup & Replication |
Replication Speed
Initial Replication
Increment Replication |
Slower
Faster |
Faster
Slower
|
ITComparison Team Comments
VizionCore vs Veeam |
We had created a 40GB Virtual
machine & then cloned it. Then we installed Veeam Backup & Replication
as well VizionCore Vreplicator on two different VMs with exactly same
specs. We had started the replication at the same time of the two 40 GB
VMs and was surprised with the result. The initial replication took
around 2 hours using Veeam & around 4 hours using VizionCore vReplicator.
Although Vizioncore took twice the time to do the initial replication,
it was a lot faster on subsequent replications. It took Vizioncore
around 3 minutes for each subsequent update where it took Veeam around
10 minutes for each subsequent update.
It seems Veeam is twice
as fast at the initial replication, where Vizioncore is four times as
fast on subsequent replications. It seems Vizioncore snapshot technology
had succeeded to keep subsequent updates super fast, but that come at
certain limitations with snapshots & so on you can find more about it in
the rest of the comparison. |
Compatibility
ESX 3
ESX 3i
ESX 4
ESX 4i
ESX 4i Free
Virtual Center 2.5
Virtual Center 4.0
Thin Provisioned disk |
Supported
Not Yet
Supported
Not Yet
Not Supported
Supported
Supported
Not Yet |
Supported
As a Replica Source only
Supported
As a Replica Source only
Not
Supported
Supported
Supported
Not Yet |
ITComparison Team Comments
VizionCore vs Veeam |
Both VizionCore vReplicator
& Veeam Backup & Replication had started to offer vSphere support.
Neither Veeam Backup &
Replicaiton nor VizionCore vReplicator support VMware ESXi as a backup
target or a replica destination. Though veeam support ESXi as a source,
which can help enviornments that must run ESXi on source, but not on
their target (DR Site). We were not able to get a commitment of either
vendor on when ESXi will be fully supported.
Both products don't work
correctly with Thin provisioned disks, they can replicate thin
provisioned disk, but the target disk will be converted to a thick disk. |
Installation Easiness |
Great |
Great |
Usage Easiness |
Great |
Great |
VSS Integration |
Yes |
Yes |
ITComparison Team Comments
VizionCore vs Veeam |
Although both support VSS
backup, its worth mentioning Veeam backup & Replication had master it
way earlier than Vizioncore vReplicator, as well in our test environment
the failover of a windows 2008 AD with vReplicator required us to go to
AD Restore mode and fix it from there, where we did not have the same
problem in Veeam. This is seems to be a known problem with vReplicator &
hope to get contacted by VizionCore staff if there is away to avoid it. |
Automatic Failover |
NO |
NO |
Automatic Failback |
NO |
NO |
ITComparison Team Comments
esxReplicator vs Veeam |
Although neither of the
products support automatic failover, our team believe its never a good
practice to use automatic failover for a Disaster Recovery. It is always
better to control the DR failover manually and have a procedure on when
to call for a disaster failover. |
Notification by e-mail, GUI,Event Log |
Yes |
Yes |
VCB
Integrated replication |
NO |
Yes |
ITComparison Team Comments
vReplicator vs Veeam Backup |
Veeam backup & replication
support a great feature which can enhance its speed and lower the affect
on the host by integrating with VCB for replication.
VizionCore vReplicator does
not provide any VCB integration for replication, although vRanger
supported it for backup. |
File level restore from replica |
No |
Yes |
ITComparison Team Comments
Veeam Replication vs
VisionCore |
This is feature has surprised our team to
be included in a disaster recovery replication solution. I mean it
really took a deep though to come up with that you might only require
some files to recover your original site instead of failing the whole
site. Being able to obtain that from your DR incase of backup failure or
not available is not a bad idea. VizionCore vReplicator still does not
offer this, but Veeam has been offering it for a while. Though this
feature is included VizionCore vRanger which is sold as a separate
license. |
Replica rollback |
NO |
Yes |
ITComparison Team Comments
Veeam vs VizionCore |
If one feature that would
really make a difference then this one must be the feature. As this will
even protect you against major virus attack & data corruption in the
main site. If you can't roll back to an earlier copy of your replication
then if your last replica is corrupt you are out of luck. I believe
Vizioncore should take a note of this feature and support it in future
release. Another thumb up for Veeam. |
Integrated Backup Solution. |
NO |
Yes |
ITComparison Team Comments |
Veeam integrate both the backup solution &
the replication solution into one product Veeam backup & Replication,
where VizionCore sell the backup solution as a separate product called
vRanger at an additional cost. |
Cost |
~$500 per VM |
~$500
per Socket |
ITComparison Team Comments
VisionCore vs Veeam |
As both vendors have taken a different
approach to their licensing schema, your mileage with their pricing will
vary. If you are planning to replicate all your VMs & have many VMs per
host then Veeam will definitely be a cheaper option. Though if you have
many VMs, but only few need to be replicated & they are scattered across
many ESX Servers then Vizioncore vReplicator might end up to be cheaper
option. - One thing to consider
as well, Veeam price include their backup software, where VizionCore
vRanger will cost an additional $500 per processor. Its some extra cost
to consider if you are looking for a backup solution as well as a
replication solution. - It seems
the current pricing model is hurting VizionCore vReplicator share of the
market, as we had received an e-mail from VizionCore informing us that
vReplicator will change its pricing model with the release of
vReplicator 3.0 in Q4 of 2009 to be ~$500 per Socket, but till then it
will still be priced at ~$500 per VM. |
SnapShot support |
NO |
Yes |
ITComparison Team Comments |
While doing our testing we had noticed that
we could not replicate Virtual Machines which have snapshots using
vReplicator while it went without problems with Veeam. Searching that we
had discovered the method vReplicator is using snapshot to get their
blazing speed is the reason behind this. |
Backup while replicating. |
Not Supported |
Supported |
ITComparison Team Comments
Veeam Replication vs
VizionCore esxReplicator |
Again it seems Vizioncore snapshoting
mechanism does not allow them to run backup while replicating. Even when
using their vRanger backup software they had to implement a mechanism
for the two products to communicate so no replication take place while
backup is taking place. If you decide you want to use another product or
just VCB to backup while protected by vReplicator you are out of luck. I
guess another cost for the blazing fast replication.
As Veeam have their replication setup
differently, they don't seems affected by this problem, as we were able
to backup the same VM with VCB without having to shut its replication.
|
Secure Replication |
Yes |
NO |
ITComparison Team Comments
Veeam Replication vs
VizionCore esxReplicator |
VizionCore transfer its data over ssh,
which secure its data transfer. If you don't trust the media your
transferring the data across then this might get to be an important
feature for you. Veeam has a
different thought & don't try to do the same. As securing the data while
transferring forbid accelerating devices from accelerating the frames.
So it depend on your need of securing
the transferred data or being able to accelerate your transfer on which
method is better. |