{"id":243,"date":"2026-01-02T03:30:10","date_gmt":"2026-01-02T03:30:10","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=243"},"modified":"2026-08-03T22:28:11","modified_gmt":"2026-08-03T22:28:11","slug":"a-complete-tutorial-on-how-to-backup-windows-vps-safely-and-efficiently","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/a-complete-tutorial-on-how-to-backup-windows-vps-safely-and-efficiently\/","title":{"rendered":"Windows VPS Backups with wbadmin and VSS: A Native, No-Cost Strategy"},"content":{"rendered":"

Hypervisor snapshots are handy, but they are not backups \u2014 they live on the same infrastructure as your VPS and disappear with it. The tool that ships with every Windows Server edition and does the job properly is wbadmin, built on Volume Shadow Copy (VSS). It is free, scriptable, and capable of full bare-metal restores. Here is how to put it to work on a Windows VPS.<\/p>\n\n

Backups need storage, and storage costs money, so the plan you choose matters. Our comparison table<\/a> shows which providers include a second data disk or cheap add-on volumes \u2014 the minimum requirement for the strategy below.<\/p>\n\n

Why VSS Matters<\/h2>\n\n

VSS coordinates with running applications \u2014 SQL Server, IIS, file services \u2014 so files are copied in a consistent state instead of a half-written mess. wbadmin drives VSS automatically, which is why a wbadmin backup is restorable in a way that a raw file copy usually is not.<\/p>\n\n

Install Windows Server Backup<\/h2>\n\n

The feature is not enabled by default on Server Core or minimal installs. One command fixes that:<\/p>\n\n

Install-WindowsFeature Windows-Server-Backup<\/code><\/pre>\n\n
Verify with Get-WindowsFeature Windows-Server-Backup | Select-Object Name, InstallState<\/code> \u2014 InstallState should read Installed.<\/p>\n\n
Your First Backup<\/h2>\n\n
Two rules before you start: the backup target must be a different volume (wbadmin refuses to back up C: to C:), and the target should be a dedicated data disk, not the OS disk. Then:<\/p>\n\n
wbadmin start backup -backupTarget:E: -include:C: -allCritical -quiet<\/code><\/pre>\n\n
-allCritical includes the System Reserved and boot volumes, which is what makes bare-metal recovery possible. The result is a VHD\/VHDX set under E:\\WindowsImageBackup\\\\ that you can also mount and browse file-by-file.<\/p>\n\n
Verify the Backup<\/h2>\n\n
A backup you have never restored is a guess. At minimum, confirm the job completed and spot-check the output:<\/p>\n\n
wbadmin get status\nMount-DiskImage -ImagePath E:\\WindowsImageBackup\\\\\\C_Volume.vhdx<\/code><\/pre>\n\n
Mounting the VHD lets you browse the backed-up file system and pull out a single file if that is all you need. When you are done, Dismount-DiskImage<\/code> with the same image path. A quarterly full restore drill is still worth doing \u2014 but the mount check catches most problems in seconds.<\/p>\n\n
Check and Automate<\/h2>\n\n
List what exists:<\/p>\n\n
wbadmin get versions<\/code><\/pre>\n\n
Then schedule a nightly run at 02:00:<\/p>\n\n
wbadmin enable backup -addtarget:E: -schedule:02:00 -include:C: -allCritical -quiet<\/code><\/pre>\n\n
Prefer more control? Skip enable backup and register a Task Scheduler job that runs the start backup command instead \u2014 identical result, easier to extend with a pre- and post-check.<\/p>\n\n
Ad-hoc backups keep every version until the target disk fills. To let wbadmin reclaim space automatically, add the -allowDeleteOldBackups switch to the start backup command \u2014 it deletes the oldest backup set only when the target runs out of room, which is the behavior you want on a small VPS data disk.<\/p>\n\n
Restore When It Counts<\/h2>\n\n
Find the version you want, then recover a volume:<\/p>\n\n
wbadmin get versions -backupTarget:E:\nwbadmin start recovery -version:08\/04\/2026-02:00 -itemType:Volume -items:C: -recoveryTarget:C:<\/code><\/pre>\n\n
For a full bare-metal restore, boot from Windows Server installation media and choose System Image Recovery \u2014 wbadmin backups are exactly what that wizard expects.<\/p>\n\n
Practice restores in a disposable VM rather than on your live server: install a fresh Windows Server trial, recover the volume from the backup, and confirm your application starts. That single exercise proves both the backup itself and your restore procedure \u2014 the two halves most backup plans never test together.<\/p>\n\n
Get the Backup Off-Site<\/h2>\n\n
A backup on a second disk of the same VPS survives a crashed OS, not a failed provider. wbadmin output is plain VHD files, so copying them off-site is trivial:<\/p>\n\n
robocopy E:\\WindowsImageBackup \\\\backup-vps\\backups$\\WindowsImageBackup `\n  \/MIR \/R:2 \/W:5 \/LOG:C:\\Scripts\\robocopy.log<\/code><\/pre>\n\n
On a VPS you often do not have a second local disk at all \u2014 in that case a cheap second VPS or object storage mounted over SMB is a perfectly valid wbadmin target.<\/p>\n\n
VPS-Specific Caveats<\/h2>\n\n