Services
Microsoft Hyper-V
VYN IT uses Hyper-V when Windows Server already carries the business software or the license does not justify another hypervisor. One host with a tested backup is the honest size for many businesses. A cluster follows when one server stopping would stop the business and shared storage exists.
VYN IT uses Hyper-V when Windows Server already carries the business software or the license does not justify another hypervisor. One host with a tested backup is the honest size for many businesses. A cluster follows when one server stopping would stop the business and shared storage exists.
Checkpoints are not backups. Virtual-machine backup sits somewhere else. Host updates happen in a window, not automatically during a deadline. The application must be supported on Hyper-V, otherwise it stays on the hardware the vendor names.
What we do
A single host
One or more virtual machines on a Windows Server, sized for RAM, CPU and disk, with reserve.
A cluster when it carries
Two hosts and shared storage, failover for the machines that must not stop. Without storage and without a test, that is not a cluster.
Moving to Hyper-V
From physical servers or another platform, in a window, with a test of the business software.
Backup
The VMs are copied off the host. A restore of one machine is tried.
Performance
Full virtual disks, too little RAM and checkpoints that have sat for weeks are made visible and cleaned up.
Technologies and solutions
Windows Server with Hyper-V
The version your licenses and the application can carry.
Short checkpoints
Before a change, then merged. Not a stand-in for backup.
Failover cluster
Only with shared storage and a test that actually moves a machine to the other host.
VM backup
An image on another target, retention, and a recipient for failed jobs.
Admin through named accounts
No local administrator password everyone in the office knows.
What you gain
It fits the Windows license
You do not buy a second hypervisor when Hyper-V carries the application.
The size is honest
One host while that is true. Two when downtime requires it.
Updates are planned
The host reboots when the window allows it, not in the middle of the day.
One machine can be restored
Not only the hardware, but the VM that runs the business application.
Typical problems
Checkpoints for months
The virtual disk has grown, storage is full, and nobody dares to merge.
A host without backup
Hyper-V runs, and the “backup” is a copy of the folder on the same disk.
A cluster on paper
Two servers, no shared storage, and failover never tried.
The application dislikes Hyper-V
The vendor names another platform, and the move happened anyway.
How we work
- 1
Advice
We check the license, the application and whether a host outage would stop the business.
- 2
Planning
Single host or cluster, storage and backup are fixed before anything moves.
- 3
Implementation
Build in a window, test the business software, try restoring one VM.
- 4
Optimization
Old checkpoints go. RAM and disks are adjusted.
- 5
Ongoing care
Patches and failed backups stay in care on business days.
Frequently asked questions
Is Hyper-V worse than VMware?
Not as a blanket rule. It is the right choice when Windows and the application support it and the license fits. Where the vendor requires VMware, we do not virtualize against that.
Is a checkpoint a backup?
No. It sits with the virtual machine. A backup is a copy on another target, opened in a test.
When is a cluster worth it?
When a server stopping would stop the business and shared storage is there or will be bought. Two PCs without that storage are not a cluster.
Can we use the current Windows Server?
If the version, RAM and disks can carry the machines and updates still arrive. A full, old host is not loaded with yet another VM.
Who may administer the host?
Named accounts. The local administrator password does not sit in a shared file.
Contact and advice
Call us or send an inquiry. We reply on business days and say whether and how we can help.
+43 1 996 96 33