<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for ITComparison.com (Blog)</title>
	<atom:link href="http://www.itcomparison.com/blg/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.itcomparison.com/blg</link>
	<description>The Best Techies Blog!!!!!</description>
	<pubDate>Thu, 11 Mar 2010 21:51:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by admin</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-193</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-193</guid>
		<description>Veeam has just announced Veeam Backup &#38; Replication which is fully supporting ESXi. For more information please check out the post at:

http://www.virtualizationteam.com/veeam/veeam-backup-replication/veeam-backup-replication-4-1-with-full-support-for-replication-to-esxi-hosts.html</description>
		<content:encoded><![CDATA[<p>Veeam has just announced Veeam Backup &amp; Replication which is fully supporting ESXi. For more information please check out the post at:</p>
<p><a href="http://www.virtualizationteam.com/veeam/veeam-backup-replication/veeam-backup-replication-4-1-with-full-support-for-replication-to-esxi-hosts.html" rel="nofollow">http://www.virtualizationteam.com/veeam/veeam-backup-replication/veeam-backup-replication-4-1-with-full-support-for-replication-to-esxi-hosts.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by admin</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-184</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 24 Oct 2009 10:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-184</guid>
		<description>Hi Frank,

We will look into providing a vRanager &#038; Veeam Backup comparison, though we started with the replication part as we have not seen any one comparing the replication products, where there is few comparisons of the backup solutions available on the net.

Enjoy,
ITComparison Team</description>
		<content:encoded><![CDATA[<p>Hi Frank,</p>
<p>We will look into providing a vRanager &#038; Veeam Backup comparison, though we started with the replication part as we have not seen any one comparing the replication products, where there is few comparisons of the backup solutions available on the net.</p>
<p>Enjoy,<br />
ITComparison Team</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by admin</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-183</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 24 Oct 2009 10:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-183</guid>
		<description>Dear Jewel,

For future release information of both VizionCore &#038; Veeam I would recommend you look at their site. We have decided to keep the comparison as much as possible to the currently compared products as we can't verify future release features. Thanks for your understanding &#038; hope you come back &#038; check our upcoming comparisons.

Enjoy,
ITComparison Team</description>
		<content:encoded><![CDATA[<p>Dear Jewel,</p>
<p>For future release information of both VizionCore &#038; Veeam I would recommend you look at their site. We have decided to keep the comparison as much as possible to the currently compared products as we can&#8217;t verify future release features. Thanks for your understanding &#038; hope you come back &#038; check our upcoming comparisons.</p>
<p>Enjoy,<br />
ITComparison Team</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by admin</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-182</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sat, 24 Oct 2009 09:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-182</guid>
		<description>Our team has been busy building another comparison lately, which was the cause of our late reply to this post. It seems stuff got heated up in here so fast, that we had missed apart of the fun. 

Ok, for people who is following up we had just modified the comparison after all the information feed to us from VizionCore, Veeam, &#038; others on our blog. We had went back to the lab and validated the technology points. As well we had a team members online gathering where we had discussed other points brought up on our blog post &#038; below what has been modified &#038; what has been left &#038; why.

ESXi support as a source disk by Veeam but not VizionCOre was added to the comparison. Although Veeam does not support ESXi as a target, we thought supporting it as a source might be an important to know for some customers.

ESXi expected full support date for both products was removed, as neither party was able to commit to the date listed on their forums. We had decided it was fair enough to remove the expected date as requested by both vendors.


Thin Provisioned disks are still not fully supported on both solutions. We had went to the lab and tried to replicate Thin Provisioned disks with both solutions, and what we had end up with was a think disk on the target side. Although that will do the DR failover trick, it will waste way more space than if thin disk provisioning was totally supported.

We had not added the compression point as requested by Veeam in the earlier comment on here, as VizionCore claim to do inline compression. As well while testing the replication we could not really calculate the compression advantage of neither vendor as both of them use a different method of replication.

We have not omitted VizionCore planned product price, as that was committed by VizionCore &#038; that will not change based on technology.

We have worked hard to verifying each of the above modifications &#038; tried to keep it as accurate as possible. If you have any points which you still think it has to be modified please point it out in the next 3 days, as we need to close the lab for this comparison. Any comment will be posted after three days it will be posted to the blog, but will not affect the comparison unless its a serious mistake.

Enjoy,
ITComparison Team</description>
		<content:encoded><![CDATA[<p>Our team has been busy building another comparison lately, which was the cause of our late reply to this post. It seems stuff got heated up in here so fast, that we had missed apart of the fun. </p>
<p>Ok, for people who is following up we had just modified the comparison after all the information feed to us from VizionCore, Veeam, &#038; others on our blog. We had went back to the lab and validated the technology points. As well we had a team members online gathering where we had discussed other points brought up on our blog post &#038; below what has been modified &#038; what has been left &#038; why.</p>
<p>ESXi support as a source disk by Veeam but not VizionCOre was added to the comparison. Although Veeam does not support ESXi as a target, we thought supporting it as a source might be an important to know for some customers.</p>
<p>ESXi expected full support date for both products was removed, as neither party was able to commit to the date listed on their forums. We had decided it was fair enough to remove the expected date as requested by both vendors.</p>
<p>Thin Provisioned disks are still not fully supported on both solutions. We had went to the lab and tried to replicate Thin Provisioned disks with both solutions, and what we had end up with was a think disk on the target side. Although that will do the DR failover trick, it will waste way more space than if thin disk provisioning was totally supported.</p>
<p>We had not added the compression point as requested by Veeam in the earlier comment on here, as VizionCore claim to do inline compression. As well while testing the replication we could not really calculate the compression advantage of neither vendor as both of them use a different method of replication.</p>
<p>We have not omitted VizionCore planned product price, as that was committed by VizionCore &#038; that will not change based on technology.</p>
<p>We have worked hard to verifying each of the above modifications &#038; tried to keep it as accurate as possible. If you have any points which you still think it has to be modified please point it out in the next 3 days, as we need to close the lab for this comparison. Any comment will be posted after three days it will be posted to the blog, but will not affect the comparison unless its a serious mistake.</p>
<p>Enjoy,<br />
ITComparison Team</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by Frank</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-181</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Fri, 23 Oct 2009 17:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-181</guid>
		<description>I would be very happy if you would expand your test (or add it as second one) in which you take a detailed look to the backup functions of the products. Your tests for replica-functions are good but this is the 2nd step for an typical environment, or not?

Veeam will offer a new version of their backup-solution which contains support for the new vSphere vStorage API in one or two weeks.

This is right timing for us because we must find the a solution for our new environment with 3 or 4 ESX Enterprise Servers while next month - at january 2010 the new servers should be ready to run and we must find and buy the best solution for it before!

In our actual (very old) environment with physical servers we use Symantec BackupExec v12. They offer an addon to backup ESX-Servers / VMs. But is it a good idea or was another solution a better choice? We try in moment the new solution from Acronis, "Backup &#38; Recovery" v10, a week ago we have seen a presentation about the bundle of a quantum DXi (with dedup) and esXpress which works as virtual appliances and it looks / sounds very smart.

We need definitely help to find the right solution but we haven't the hardware and the time to make all the needed tests for different products on market. Your site and you was the only help, because no other does compare the products... :-)

A big point for us is the support for MS SQL 2005 / 2008 and Exchange 2007. Both products should have VSS-Support but is it enough to make consistent backups of these servers? What is with logfiles? While a "normal" backup with integrated mechanism you can cut them after backup. Is this also possible when I use "Veeam Backup" or "ESX Ranger" with VSS? If I follow the message from Anton from Veeam above VSS isn't VSS...why that? I thought it is a standard API?</description>
		<content:encoded><![CDATA[<p>I would be very happy if you would expand your test (or add it as second one) in which you take a detailed look to the backup functions of the products. Your tests for replica-functions are good but this is the 2nd step for an typical environment, or not?</p>
<p>Veeam will offer a new version of their backup-solution which contains support for the new vSphere vStorage API in one or two weeks.</p>
<p>This is right timing for us because we must find the a solution for our new environment with 3 or 4 ESX Enterprise Servers while next month - at january 2010 the new servers should be ready to run and we must find and buy the best solution for it before!</p>
<p>In our actual (very old) environment with physical servers we use Symantec BackupExec v12. They offer an addon to backup ESX-Servers / VMs. But is it a good idea or was another solution a better choice? We try in moment the new solution from Acronis, &#8220;Backup &amp; Recovery&#8221; v10, a week ago we have seen a presentation about the bundle of a quantum DXi (with dedup) and esXpress which works as virtual appliances and it looks / sounds very smart.</p>
<p>We need definitely help to find the right solution but we haven&#8217;t the hardware and the time to make all the needed tests for different products on market. Your site and you was the only help, because no other does compare the products&#8230; <img src='http://www.itcomparison.com/blg/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>A big point for us is the support for MS SQL 2005 / 2008 and Exchange 2007. Both products should have VSS-Support but is it enough to make consistent backups of these servers? What is with logfiles? While a &#8220;normal&#8221; backup with integrated mechanism you can cut them after backup. Is this also possible when I use &#8220;Veeam Backup&#8221; or &#8220;ESX Ranger&#8221; with VSS? If I follow the message from Anton from Veeam above VSS isn&#8217;t VSS&#8230;why that? I thought it is a standard API?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by A Potential Customer</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-178</link>
		<dc:creator>A Potential Customer</dc:creator>
		<pubDate>Fri, 16 Oct 2009 23:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-178</guid>
		<description>Oh and full ESXi support, some of us dont want the overweight ESX running. We dont like having to patch servers so ESXi is our choice.</description>
		<content:encoded><![CDATA[<p>Oh and full ESXi support, some of us dont want the overweight ESX running. We dont like having to patch servers so ESXi is our choice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by A Potential Customer</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-177</link>
		<dc:creator>A Potential Customer</dc:creator>
		<pubDate>Fri, 16 Oct 2009 23:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-177</guid>
		<description>As a potential customer looking at both products I liked the review, a little hard to understand the English but hey its readable.

What I noticed in both product managers replies is how Veeam seem to like to beat up Vizioncore. Come on guys say positive things about your own software and dont bash the other. Thats our job as customers.

I agree that the ability to power on a vm in isolation is important, how else will you be able to tick the box in your audit that states 'dr environment tested and works'. Vizioncore take note before I fork out for my 24 enterprise cpu licenses...

What I would like;

dedup
compression and network throttling
failover and failback
better linux support
Ability to purchase direct!</description>
		<content:encoded><![CDATA[<p>As a potential customer looking at both products I liked the review, a little hard to understand the English but hey its readable.</p>
<p>What I noticed in both product managers replies is how Veeam seem to like to beat up Vizioncore. Come on guys say positive things about your own software and dont bash the other. Thats our job as customers.</p>
<p>I agree that the ability to power on a vm in isolation is important, how else will you be able to tick the box in your audit that states &#8216;dr environment tested and works&#8217;. Vizioncore take note before I fork out for my 24 enterprise cpu licenses&#8230;</p>
<p>What I would like;</p>
<p>dedup<br />
compression and network throttling<br />
failover and failback<br />
better linux support<br />
Ability to purchase direct!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by Jewel</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-175</link>
		<dc:creator>Jewel</dc:creator>
		<pubDate>Wed, 14 Oct 2009 15:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-175</guid>
		<description>Great post and follow-ups. Now we have a good understanding of what we have today, and to some degree of what's coming.  I certainly do care about the future and am curious to hear more about "lotsa great new features" in Anton's post if details are available.</description>
		<content:encoded><![CDATA[<p>Great post and follow-ups. Now we have a good understanding of what we have today, and to some degree of what&#8217;s coming.  I certainly do care about the future and am curious to hear more about &#8220;lotsa great new features&#8221; in Anton&#8217;s post if details are available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by Anton Gostev</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-173</link>
		<dc:creator>Anton Gostev</dc:creator>
		<pubDate>Tue, 13 Oct 2009 19:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-173</guid>
		<description>Ah, I wish I could correct some formatting and typos in my reply above... cannot do this! :)</description>
		<content:encoded><![CDATA[<p>Ah, I wish I could correct some formatting and typos in my reply above&#8230; cannot do this! <img src='http://www.itcomparison.com/blg/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VizionCore vReplicator vs Veeam Backup &#038; Replication by Anton Gostev</title>
		<link>http://www.itcomparison.com/blg/?p=56#comment-172</link>
		<dc:creator>Anton Gostev</dc:creator>
		<pubDate>Tue, 13 Oct 2009 19:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.itcomparison.com/blg/?p=56#comment-172</guid>
		<description>A few comments from Veeam side:

1. Veeam supports ESXi as replica source, Vizioncore does not support ESXi at all. You would think - no big deal? But we have 

customers who are 100% on ESXi in their production, while using single "full" ESX as standby host because this is what our product requires - and they are quite happy. Can Vizioncore work in such environment? No. Thus, I believe our ESXi support on source is very important and must be reflected in comparison.

2. You said both products has VSS integration, but they are dramatically different as for depth and maturity. You have even run into the actual issue demonstrating that Vizioncore approach to VSS integration is flawed, and does not let the product produce *working* replicas. Forget about all the other features both products have, and please tell me: what is the use from replication products that produces replicas which cannot be powered on in case of emergency without manual intervention? To me, this issue alone means big red sign to any DR product, no matter how fast it is, and how great other features are. More on this here: http://veeammeup.com/2008/08/vss-and-vmware-esx-what-your-vmware-backup-vendor-isn%E2%80%99t-telling-you.html (and 

you've run into the actual issue yourself anyway).

3. What I believe is extremely important for a replication product, but not mentioned in this comparison, is network traffic compression. Would you agree that this feature is absolutely critical for WAN replication? Now Veeam has it, Vizioncore does not have it.

Other than this above, comparison looks good, thanks for being objective to both vendors.

On a side note:
a) "Though both are promising to support [ESXi] in 1st half of 2010" - are you sure you heard about this from Veeam? I am actually product manager for Veeam Backup and Replication, and I am a bit surprised to see this statement. I am also surprised to see this statement from Vizioncore given the recent post on their forum from one of their officials stating H2 2010 timeframe for ESXi support. OK OK, I will mind my own business here ;)

b) Thank you for NOT updating comparison with the next version's features. Some companies out there love to sell future. I would even kindly ask you to remove the pricing change remark. Let's deal only with software that is available for download today, and prices you have to pay if you would by the software today. Would you agree? Up to you, of course.

Yes, we are also releasing new major release of our product later this month with lotsa great new features, but it does not matter for this specific comparison, right?

I think this is it from my end, and yet again - great job - thanks so much for taking time to evaluate both products and post such a great summary. It will be even better if you consider some of my bullets above ;)</description>
		<content:encoded><![CDATA[<p>A few comments from Veeam side:</p>
<p>1. Veeam supports ESXi as replica source, Vizioncore does not support ESXi at all. You would think - no big deal? But we have </p>
<p>customers who are 100% on ESXi in their production, while using single &#8220;full&#8221; ESX as standby host because this is what our product requires - and they are quite happy. Can Vizioncore work in such environment? No. Thus, I believe our ESXi support on source is very important and must be reflected in comparison.</p>
<p>2. You said both products has VSS integration, but they are dramatically different as for depth and maturity. You have even run into the actual issue demonstrating that Vizioncore approach to VSS integration is flawed, and does not let the product produce *working* replicas. Forget about all the other features both products have, and please tell me: what is the use from replication products that produces replicas which cannot be powered on in case of emergency without manual intervention? To me, this issue alone means big red sign to any DR product, no matter how fast it is, and how great other features are. More on this here: <a href="http://veeammeup.com/2008/08/vss-and-vmware-esx-what-your-vmware-backup-vendor-isn%E2%80%99t-telling-you.html" rel="nofollow">http://veeammeup.com/2008/08/vss-and-vmware-esx-what-your-vmware-backup-vendor-isn%E2%80%99t-telling-you.html</a> (and </p>
<p>you&#8217;ve run into the actual issue yourself anyway).</p>
<p>3. What I believe is extremely important for a replication product, but not mentioned in this comparison, is network traffic compression. Would you agree that this feature is absolutely critical for WAN replication? Now Veeam has it, Vizioncore does not have it.</p>
<p>Other than this above, comparison looks good, thanks for being objective to both vendors.</p>
<p>On a side note:<br />
a) &#8220;Though both are promising to support [ESXi] in 1st half of 2010&#8243; - are you sure you heard about this from Veeam? I am actually product manager for Veeam Backup and Replication, and I am a bit surprised to see this statement. I am also surprised to see this statement from Vizioncore given the recent post on their forum from one of their officials stating H2 2010 timeframe for ESXi support. OK OK, I will mind my own business here <img src='http://www.itcomparison.com/blg/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>b) Thank you for NOT updating comparison with the next version&#8217;s features. Some companies out there love to sell future. I would even kindly ask you to remove the pricing change remark. Let&#8217;s deal only with software that is available for download today, and prices you have to pay if you would by the software today. Would you agree? Up to you, of course.</p>
<p>Yes, we are also releasing new major release of our product later this month with lotsa great new features, but it does not matter for this specific comparison, right?</p>
<p>I think this is it from my end, and yet again - great job - thanks so much for taking time to evaluate both products and post such a great summary. It will be even better if you consider some of my bullets above <img src='http://www.itcomparison.com/blg/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
