We’ve heard that some people are having issues registering on our forums. We do apologize for that but in an effort to keep out spam we have to dis-allow certain email domains (gmail, hotmail) and we also have a CAPTCHA that has been made a bit more user friendly (black and white instead of color). I didn’t realize until just the other day that some color CAPTCHA’s are very difficult for people who are color blind.

Anyway, vote for your favorite and be sure to leave a comment. There’s a bonus prize of a Flip going to the person with the best comment.

So, for just shy of 1K you get fully licensed vSphere. This is great but it still leaves you without an efficient backup and recovery tool, single pane of glass monitoring or detailed reporting…enter Veeam Essentials bundle…offering Veeam Backup & Replication, Veeam Monitor and Veeam Reporter for around US $2,000 (Americas pricing). The Veeam Essentials bundle is fully functional licensed versions of those 3 products for 6 sockets (3 hosts).

Of course Veeam is placing some limits on this bundle…

• Must be purchased with VMware vSphere Essentials (or proof of VMware vSphere Essentials must be given)
• Each bundle will only support 6 sockets. This means that even if you purchase multiple bundles, each Veeam product will only work on 6 sockets, you’ll need to install other instances with the other license(s) to manage the other VMware vSphere Essentials vCenters.
• Each bundle is 6 sockets, no less (sorry folks, you can’t get it cheaper for only 4 sockets)

What does all this mean? For just under US $3,000 (hardware not included) you get 6 sockets of VMware vSphere, 6 sockets of Veeam Backup & Replication, 6 sockets of Veeam Monitor and 6 sockets of Veeam Reporter. That’s 3 servers with up to 8 cores (2×4) and 256GB RAM each running VMware ESX(i). Couple that with a free iSCSI solution such as Starwind and now you’re talking 2 TB of shared data for free (hardware and Windows licensing not included).

I did not include Support and Subscription (SnS) above because for VMware vSphere Essentials it’s optional (it’s not optional on VMware vSphere Essentials Plus). Veeam’s Essentials bundle includes 1 year of support and upgrades in the list price.

Now, let’s discuss a few things about the Free Version of ESXi. We’ve gotten a number of questions on this since we released the “news” and the Essentials bundle on the same day. Below is a simple table explaining what is and isn’t supported:

Table of compatibility:

+ = supported/usable
-  = not supported

Now please note that Veeam will not be supporting ESXi Free 4.0 at all. If you’re a current customer using Veeam Backup & Replication for ESXi Free 3.x, please contact your Veeam ProPartner or sales person for vSphere options.

While I don’t endorse or condone any of the following, I thought I would be doing an injustice if I did not include links to the community’s reaction to our announcement regarding dropping ESXi Free support. The list below is just some of the reaction, be sure to read the comments in each as well.

Rick Vanover at Virtualization Review

Rich Brambley at VMETC

Eric Scholten at VMGURU.NL

Gabes Virtual World

Search Server Virtualization’s Alex Barrett

Rich Brambley at VMETC again after Alex Barrett’s post

Search Server Virtualization’s Eric Siebert

Edward L Haletky’s The “soon to be launched” Virtualization Practice

The comments to my post on the original announcement

Update: June 12, 2009 – New Links

Bridget Bothelo over at Virtualization Pro

Discussion over at ars technica (I noticed this in my referral stats)

Update: June 15, 2009 – New Links

Search Server Virtualization’s weekly Podcast: VMware cuts free ESXi hypervisor support, fuels battle vs. Hyper-V

Update: June 26, 2009 – New Link

Mike Stokes over at eGroup

Update: July 3, 2009 – New Link

Tom Howarth over at PlanetVM

Mike Laverick from RTFM

The idea behind Veeam’s PowerShell Extensions is to allow people who want to query vCenter using a PS script to query Veeam’s Reporter Enterprise database instead. We wanted to provide an easy way to do this without having to completely re-write pre-existing scripts that have been written for the VI Toolkit. Another advantage is that Reporter Enterprise saves “points-in-time” of your Virtual Infrastructure, so if you want to run a PS script comparing last month to this month, the data is there, it’s just a matter of connecting to it.

In the process, we ended-up messing with the Verb-Noun syntax of PowerShell and we understand (now) that the PowerShell community will not be happy with this. For instance, in the VI Toolkit you have the command “Get-VM”. Rather than change the noun (VM) Veeam decided to change the verb, so with the Veeam PS Extensions the command is “_Get-VM”. Essenitially all the verbs that can be used in the VI Toolkit can be used with the Veeam Extensions just by adding an “_” in front of the verb.

We understand now that this is wrong and we will be working to fix it. One suggestion is to leave the verb alone and change the noun so that we would have “Get-VRVM” where the VR=Veeam Reporter. Another suggestion is to use “Veeam\Get-VM”. Both of these options are valid, what do you think? We’d love to know your feedback!

Hal Rottenberg has invited me to be on his PowerShell podcast on April 30 and I’m looking forward to being there and talking about how we’ve implemented this and getting suggestions for how to improve it.

You can check out the Veeam Reporter Enterprise User Guide for a full description of the PowerShell Extensions.

Thanks,

-doug