ESXi free is limited, 8 vcpu per VM and that limit can be easily reached limit.
It's easily reached if you starve a VM of IOPS or RAM and it's spinning cycles waiting on IO. In reality VERY few things need 8 vCPU. I've seen The ONLY exchange server for 5000 users not need that many resources.
Given modern Skylake hardware, and 4Ghz Intel Xeon Cores's if your hitting the 8vCPU limit I'm REALLY curious why your not willing to spend the one time ~$200 per host that is the Essentials bundle to get some more features is a rounding error in your budget (it's like less than a $1 a day per host).
Keep in mind it is not per hosts, but ~$600 per three hosts, so for much of the SMB that's either $300 or $600 per host and makes things like future upgrades potentially a problem. And $600 per host is enormous for the SMB market. Absolutely staggering. Given that 90% of the market can't even cost justify a server, let alone a server with that much additional licensing.
On a single host, how much value is that $600 getting an SMB versus getting free, unlimited use virtualization with $600 of faster hardware? When we are talking a $3,000 server, an extra $600 is anything but trivial.
The "only $200 per host" is really "holy crap, $200 per host with a minimum of three!!" That's not at all a small number, not in the SMB market. And especially not in an SMB market outside of the US.
I still love XenServer and XenOrchestra as my one of choice for now. But then i'm only running small Linux/Windows servers on it anyway like Zabbix, Radius, Unifi. Nothing full production like the DC or Dynamics/SQL
@Kelly i have seen the feature matrix, and that's why i asked.. because there are two editions in feature matrix.. but @DustinB3403 said above that the matrix includes support.. is this correct or not?
The matrix is from Citrix, not XenServer. It is really confusing terminology.
Standard and community are the same. The only difference is standard has support from Citrix.
Enterprise and the features listed there are only available to those with a paid support subscription for that version.
The codebase may be identical, but you can't access things like GPU virtualization without the Enterprise version.
Even more confusing is that those things are add one rather than unlocks... so it isn't really xenServer doing it.
KVM with Virtmanager.
Centos latest is my preferred KVM host.
And Fedora LXDE Spin is my preferred Virt-Manager choice, I use it from inside Windows using Virtualbox.
Cause it resembles the old ESXi Philosophy with Vsphere C# client
And you can do whatever you want with it, and for free. Especially when you use virt IO drivers for network and disk, you get nearly identical bare metal speeds.
But sadly its lacking other tools to allow users to connect and use the VM, you will have to do this from inside the VM like RDP and VNC.
Wouldn't that mean exposing your XS to the internet? I suppose not if you lock the inbound ports to the IP of the XO, where ever it's hosted. So from a management point of view, that's great, but I don't think most would end up using the backup portion in that situation, soooo...
How is this different from using (as an example) the built-in replication tool in Hyper-V? Either way you still need the 'net?
I've never tested this, so I am working from an assumption. But upon the assumption here is my explanation.
You have a XS host in your office in Dallas, 100 Mb internet connection.
The MSP has a XO VM running in a hosted DC in Cali that's used to manage the XS host. How does the data flow to the backup target? Does it flow through the XO system then to the target? I know that Veeam works this way. Assuming it does flow through the XO box, the data would flow out the 100 Mb connection to the XO, and then to where ever the backup target is. Assuming that's at the customer site, that would also be on that single 100 Mb connection.
Again - I admit to an assumption here - if my assumption is wrong, please don't be an ass about it, just inform me, and the rest here.
So with that assumption, assuming you want your first backup target to be onsite, then you'd either need a separate backup solution, or another copy of XS locally that runs backups inside the network.
Actually, no, Veeam does not work that way.
By default, the paid version of Veeam installs proxy stuff on each host as well as the box that Veeam is installed on. When a backup job runs, it chooses the best place to run through each time unless you specify a specific option in the backup job.
In scenarios such as these what would be the recommended backup approach: DAS, NAS, Backup Appliance, lower end server, removable disk storage, tapes (intentionally left out cloud)?
Should be separate (physically!) entity non-related to your production cluster. Cheap NAS is OK.
For the average scenario (and I really just mean average) it's Synology or ReadyNAS that I recommend. Easy, supported, cost effective, desktop or rackmount options, well known, good brands, nice features.