Virtual Server Backup: Adding Your Clients’ VMs to the Service You Already Run

Deploy your branded agent inside each Windows or macOS VM, exactly as you would on a physical server. Then a client stands up two Windows VMs on a Hyper-V or VMware host, moves QuickBooks and a SQL database onto them, and asks whether “those are backed up too.” Virtual server backup is not a new product you have to go sourced. It is the same service you already sell, extended to the machines your clients are increasingly running virtually.

Here is how virtual servers fit into your backup service, what to charge for them, and how to prove a restore before you need one.

A virtual server is still a server your client depends on

From the virtualization host’s perspective, a VM is represented by a collection of virtual disks and configuration files. From your client’s perspective, however, it is a production server; the machine that runs their accounting, their line-of-business app, or their SQL database. When it goes down, the call you get on Wednesday morning is identical to a bare-metal failure, and so are the recovery expectations.

Two things make virtual servers worth pulling into your service deliberately:

• Consolidation risk. Multiple workloads can depend on the same physical host and storage infrastructure. A host failure, storage failure, ransomware incident, or configuration problem can therefore affect multiple VMs simultaneously.
• Recurring revenue. Every VM you protect is another endpoint on your per-seat billing. Because servers bill the same as workstations on the platform, adding a client’s VMs does not blow up their price or shrink your margin.

How you back up a client’s virtual servers

The approach is the same one you use for physical machines, which keeps your workflow and your client’s experience consistent.

Deploy your branded agent inside each Windows or macOS VM, exactly as you would on a physical server. The VM shows up as one more endpoint in your Backup Ops console alongside everything else you manage, so every client’s virtual and physical machines sit in one view with the same alerts and reports.

What comes with each server endpoint, at no extra SKU:

• SQL and Exchange jobs for the database and mail VMs, so you are protecting the application, not just the files underneath it.
• Full disk image and bare-metal restore, so you can rebuild a downed VM onto fresh virtual hardware, not just pull individual files back.
• Your choice of storage. Point the client’s jobs at Wasabi, Backblaze B2, Amazon S3, Google Cloud, or Synology C2 and pay the cloud vendor directly. There is no storage markup on the platform, so the margin decision stays yours.

The default architecture most partners run: branded agent in the VM, an encrypted cloud copy offsite for the disaster case, and a local vault on the client’s NAS or a nearby endpoint for fast file pulls. If a client has data-residency or regulatory requirements, select a storage region and backup configuration that aligns with those requirements. For HIPAA-regulated environments, backup storage is only one component of the organization’s broader compliance program.

Prove the restore before your client needs it

Backing up a virtual server is the easy half. The half that matters is the restore, and it is worth building into your onboarding for every VM you take on.

• Test a real restore. Pull the disk image down to a spare host or a new VM and boot it. You want to know your bare-metal restore works on this client’s setup before the day the host dies, not during it.
• Keep point-in-time versions. Ransomware that reaches a VM should not reach your offsite copies, and you want a version from before the infection to roll back to. The offsite encrypted copy plus retained versions is what turns a bad Tuesday into a routine restore.
• Match the policy to the asset. A file-server VM gets image plus file jobs. A SQL VM gets SQL jobs. Do not run one blanket policy across every VM on the host.
• Throttle during business hours. Image jobs on large VMs are heavy, so cap upload speed during the workday, especially when the client’s connection is shared with staff.
• Watch it daily. The point of one console is that a missed job on any client’s VM surfaces in the same morning check you already do.

Fold it into what you already sell

You do not need a separate line of business for this. Pilot virtual server backup on one client, prove the restore, then price the VMs the same per-seat way you price the rest of that client’s endpoints. To your client it is the same branded service they already trust, now covering the machines they moved to virtual.

If you would rather keep the vault on your own hardware instead of a cloud bucket, WholesaleBackup Server runs on a Windows box and gives you that option, though most partners we see run cloud offsite plus a local vault.