virtualization & Proxmox
Migration from VMware to Proxmox, cluster design and backup solutions that have been genuinely tested for restoration. For companies in Prague and the surrounding area.
// why this is being addressed now
Following Broadcom's acquisition of VMware, standalone licences disappeared and were replaced by subscription bundles. Many companies now pay significantly more for the same environment and are looking for alternatives. Proxmox VE is the most common answer: an open-source hypervisor that delivers the same performance on identical hardware without a core licence fee.
// what we do for you
Migration of virtual machines from ESXi or vSphere to Proxmox. One at a time, always with the option to revert. We also handle Hyper-V and physical servers (P2V).
How many nodes, what storage, where the quorum will be located and what happens when the power fails. A design tailored to your size, not based on a catalogue.
Proxmox Backup Server with deduplication, off-site copies and, above all, regular restore testing. A backup that has never been tested for restoration is not a backup.
Updates, pre-intervention snapshots, monitoring of nodes, capacities and disk status. We resolve issues before full storage affects operations.
New servers from templates, configured via Ansible. A server is ready in minutes and always looks the same, including security settings.
If you already have virtualisation in place: we will review backups, updates, capacities and potential failure points. You will receive a specific list of items to fix.
// how migration is carried out
$ migration esxi → proxmox · return possible at any stage
We document the equipment, its load, dependencies, and which units may briefly go offline and which must not.
How many nodes, what storage, where backups. Schedule for nightly maintenance windows and a transparent price in advance.
Before any changes are made, a verified backup exists. Not only was it created, but it can also be restored from.
First the non-critical ones, where the procedure is fine-tuned. The original environment remains in place until the new side is running.
Documentation, training, and either you take over or we monitor it under an SLA.
// INDEPENDENT OPERATION
Our own services, monitoring, backups, PBXs and websites, run on Proxmox, which we manage using the same procedures we offer you. This includes backups to a separate backup server and off-site copies.
So we also know what isn't written in the documentation: what happens when the disk fills up at night, how long recovery actually takes, and why snapshots aren't created only after an incident.
operated by Let IT Bee, s.r.o.
// frequently asked questions
Following Broadcom's acquisition of VMware, standalone licenses were discontinued and replaced by subscription packages, often with higher minimum core counts. For many smaller companies, the cost for the same environment increased significantly. Proxmox VE is open source with no licensing fee for the core; payment is optional only for the repository of stable updates and support.
No. Virtual machines are converted one by one, always after a verified backup. The original VMware environment remains operational until the new side runs as intended, so there is a fallback option. We plan to switch outside working hours.
For smaller infrastructure with up to approximately ten virtual machines, the process typically takes several nights. The duration depends on data volume, storage speed, and how many services can tolerate a brief restart. You will receive the specific schedule in the proposal before work begins.
Normal operation is fine: the web interface is clear. The tricky parts are those that only surface during a crisis: quorum in the cluster, tested recovery from backup, and updates without downtime. We can configure these elements to run without your involvement or keep them within the SLA.
This covers most cases and is perfectly acceptable. A high-availability cluster requires three nodes, but even a single well-backed-up server is significantly better than an unbacked-up hypervisor. The design always matches what makes sense for your size: not a catalogue.
Yes. The procedure is the same: analysis, deposit, disk migration, testing, cutover. Physical servers are converted to virtual machines (P2V), which also provides an opportunity to retire hardware that no one dares to reboot.
non-binding consultation · we will review your licences, servers and backups