The Virtualization Room

Jun 10 2010   5:27PM GMT

Vizioncore, Veeam get vicious

Colin Steele Colin Steele Profile: Colin Steele

When it comes to virtualization feuds, VMware vs. Microsoft grabs all the headlines. But that doesn’t mean it’s the only game in town.

Two leading third-party management vendors — Veeam and Vizioncore — are now going at it as well. Vizioncore kicked off the fracas last week with an attack on Veeam, saying its “poorly designed architecture for data backup will undermine a virtual environment.”  In a 1,900-word blog post, Vizioncore took Veeam Backup and Replication 4.1.1 to task for several of its technical features (or lack thereof). The post also included some more, um, provocative statements.

In the intro, Kelly Polanski (who works for WaveBreak Marketing and blogs for Vizioncore) downplayed Veeam as a “small company.” She pointed out that Veeam is a privately held company based in Russia — as opposed to Vizioncore, which is owned by public company Quest Software and is “obligated to provide audited reporting of company financials.” And later, Vizioncore’s Jason Mattox called out Veeam for using unpublished VMware API calls — an issue that has caused some friction between Veeam and VMware in the past.

Veeam’s Doug Hazelman fired back the following day, calling Vizioncore’s blog a “desperate” attempt to attract customers because the Vizioncore brand is “going away soon.” (Quest plans to give Vizioncore the far-less-catchy name of “Quest Software Server Virtualization Management Group” this summer.) He also noted Polanski’s affiliation with “a company that is known to be a ‘pay for play’ blogger service and we assume the only place Vizioncore could turn to for something positive about their product.”

Oh snap!

Sensing an opportunity, another third-party management vendor, VKernel, also jumped into the fray. Chief Marketing Officer Bryan Semple reached out to potential customers on Facebook this week.

“While these two feud, we are just going to keep our head down, completely focused on solving the very complex problem of capacity management in a VMware or Hyper-V environment,” he wrote.

Debate between competing vendors is good when it focuses on technical merits, performance, cost and other issues that truly affect customers. But what about the kind of sniping that’s happening here? Vizioncore and Veeam are both well-known vendors in the virtual server infrastructure management market. They don’t need to get people talking by slamming each other over what country they’re based in or who writes their blogs.

The fact that Vizioncore and Veeam have decided to take the low road, however, shows just how heated the competition is in the third-party management market. Virtual server infrastructures are getting more complex. Admins are realizing that their hypervisor vendors can’t provide all the management tools they need. Filling that gap presents a major opportunity.

In this context, you can kind of understand why the vendors would look for any reason possible to put each other down.

But for most customers, it doesn’t matter if Veeam is based in Moscow, Russia or Moscow, Idaho. And it doesn’t matter if Kelly Polanski or Kelly Kapowski is writing blogs for Vizioncore.

1  Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • BackupChain
    I disagree. These companies are based abroad but present themselves as American, even if not expressly state such thing. Customers have a right to know where their money is going, and whether it goes abroad
    20 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: