Local teams serve Vancouver, Edmonton and Calgary. Call (604) 813-7881 for a free consult with Tony. No pressure, no jargon.
Why dental clinics should run their server on Hyper-V
Why dental clinics should run their server on Hyper-V
Many clinics run their practice software straight on one physical server. Hyper-V adds a layer of safety and flexibility underneath it. When we restore a failed server from local storage with Hyper-V and Veeam, it has taken less than 2 hours. Here is what that means, in plain words.
What is Hyper-V, and why does it matter in a dental clinic?
Hyper-V is Microsoft’s virtualization technology, built into Windows Server. It lets one physical server, called the host, run one or more virtual machines. Each virtual machine behaves like its own server, but it’s stored as files that can be backed up, checkpointed, copied and moved to other hardware. Your practice database, images and patient data matter too much to be tied to a single box.
One physical host, or Hyper-V
One physical host, no Hyper-V
- Practice software, imaging and other roles share one operating system.
- The server is tied to that specific hardware.
- A failed host means rebuilding the operating system and software on new hardware.
- No checkpoints, so upgrades are harder to test and to undo.
- Backing up the whole machine is harder, and restores are slower.
- Older operating systems stay stuck on older hardware.
Hyper-V
- Each role can run in its own virtual machine, such as the practice software database and imaging.
- Virtual machines aren’t tied to one box and can move to new hardware.
- A virtual machine can be backed up as a whole and restored elsewhere.
- A short lived checkpoint can be taken just before an upgrade, as a quick way back alongside a tested backup.
- Upgrades and moves can be planned and smoother.
- An older system can keep running on new hardware while you plan its replacement.
Everything tied to one box
If the hardware fails, everything on it stops with it.
Whole machines you can move
Back up the whole server and restore it on other hardware.
The day a single host fails
Everything on it stops together: practice software, imaging and shared files. Recovery usually means rebuilding Windows and the software on new hardware, while the clinic waits. With Hyper-V, the virtual server is restored from backup onto other hardware instead.
What Hyper-V doesn’t do
Hyper-V doesn’t remove every risk, and we don’t promise zero downtime. The host is still hardware, and a host that fails still needs repair or a restore onto other hardware. A checkpoint is a short lived way back, not a backup, and it’s not used to restore a domain controller or to undo days of new database entries. You still need tested backups, kept offsite.
How we lay out the servers
A typical build has at least 2 virtual servers. One handles identity, which means who is allowed to sign in (the domain controller). The other is a dedicated app server that runs your software. We never run applications on the domain controller. One domain controller is our usual setup for clinics that can handle a few hours of downtime, backed by tested restores. If you can’t afford any downtime, we offer a second one. Your call. We explain the trade-off up front so you can choose with your eyes open.
Windows Server licensing is part of the plan. We license Windows Server Standard or Datacenter edition to cover the virtual servers. People and devices that connect to the servers also need Windows Server access licenses (CALs), which are separate from the server license, and remote desktop sessions need their own RDS CALs. We confirm exactly what you need for your setup.
We plan around your software and imaging
Hyper-V is a must have for a business clinic, and it’s great for any production environment. We plan the move around your software and imaging setup, take and test a backup first, and do the work around your clinic hours. Benson Hunt is independent IT support, not the software vendor.
A good time to make the move
A software move, a new server or a new clinic is the natural moment to put Hyper-V in place. See the dental software conversion matrix and the dental software data conversion guide. The same idea applies to every business: read why every business should run on Hyper-V.
Why it matters, in plain words
The tech behind this page, and why it’s there. See all the plain guides.
RAID 10
Why two healthy drives still aren’t a backup
RAID 10 keeps the server running when a drive dies. It also copies a mistake or ransomware to every drive instantly.
Immutable backups
Why ransomware goes after the clinic’s backups first
Without backups, the clinic has to pay or rebuild. Our copies are locked for 30 days, and no one, not even us, can delete them early.
Multi-factor sign in
Why a stolen password shouldn’t open the clinic’s email
Passwords leak. A second check on a phone or a security key stops most stolen passwords from working.
Hyper-V questions we hear
Is a checkpoint the same as a backup?
No. A checkpoint is a short lived restore point on the same host, taken just before a change and removed once the change is confirmed. Microsoft advises against using checkpoints as a permanent recovery solution. You still need separate backups kept offsite, with test restores.
Will our practice software work on a virtual machine?
Most practice software works on a VM, and we confirm your version first. We build the server on Hyper-V and plan around your software and imaging setup before anything changes, with a tested backup first.
Can our existing server be moved to Hyper-V?
Often it can, either by converting the existing server or by building a new virtual machine and moving the software across. We review your server, take a tested backup first and plan the work around clinic hours. Ask us about yours.