Data loss on a Windows VPS is rarely caused by hardware failure. In practice it comes from bad updates, accidental deletions, ransomware, and misconfigured scripts \u2014 all of which are preventable with a working backup plan. Windows Server already ships the three tools you need: Windows Server Backup for file-level and system-state backups, the Volume Shadow Copy Service (VSS) for consistent snapshots, and robocopy for moving copies offsite. No paid backup agent required.<\/p>\n\n\n\n
A backup strategy only matters if the underlying server is dependable \u2014 check uptime guarantees and storage options when you compare Windows VPS providers on our comparison table<\/a>. Once the host is solid, the steps below give you a tested, native backup stack.<\/p>\n\n\n\n Windows Server Backup is an optional feature, not installed by default on most VPS templates. Enable it with a single command or through Server Manager > Add Roles and Features:<\/p>\n\n\n\n The feature adds the The Volume Shadow Copy Service coordinates with VSS-aware applications \u2014 SQL Server, Active Directory, Exchange \u2014 so they flush pending transactions before the snapshot is taken. A VSS backup of a database is crash-consistent in a way a raw file copy never is. Before you schedule anything, check that all writers report healthy:<\/p>\n\n\n\n Every writer should show A scheduled backup with Windows Server Backup keeps a rolling set of versions and ages out old ones automatically based on the target disk’s space. To control retention explicitly, run Before any risky change \u2014 a CU install, a schema migration, a permission overhaul \u2014 take a manual backup and a lightweight snapshot:<\/p>\n\n\n\n The An on-VPS backup disk protects against accidental deletion but not against losing the entire instance. The fix is an offsite copy \u2014 a second location that survives the primary host failing. Robocopy is the workhorse: it mirrors the WindowsImageBackup folder to a mounted network share or an object-storage drive with restartable, logged copy semantics:<\/p>\n\n\n\n Run that command from a scheduled task after the backup completes, and monitor the log path for failures. Add a second rotation layer by keeping daily copies for seven days, weekly copies for a month, and a monthly copy offsite \u2014 the An untested backup is a guess. List available versions and practice a file-level restore to an alternate location at least once per quarter:<\/p>\n\n\n\n Verify three things on each test: the restored file opens correctly, the system-state restore boots (test it on a scratch instance), and the offsite copy matches the local one ( Windows Server Backup plus VSS covers consistency, a second disk covers local resilience, and a robocopy mirror covers the offsite requirement \u2014 all native, all scriptable, all free. Install the feature, schedule the backup, mirror it offsite, and test a restore quarterly. When you pick or renew a host, make sure it offers a second attachable disk and snapshot support \u2014 see the full specs and pricing<\/a> on the Windows VPS comparison table before you commit.<\/p>\n\n\n\n Database Mart provides Windows VPS plans with extra attachable storage and snapshot options for your backup targets \u2014 check Database Mart Windows VPS plans<\/a> for storage-friendly configurations.<\/p>\n","protected":false},"excerpt":{"rendered":"Install the Windows Server Backup Feature<\/h2>\n\n\n\n
Install-WindowsFeature -Name Windows-Server-Backup -IncludeManagementTools\nGet-WindowsFeature Windows-Server-Backup | Select-Object Name, Installed<\/code><\/pre>\n\n\n\nwbadmin<\/code> command-line tool and the Windows Server Backup<\/strong> snap-in. On a VPS, attach a second virtual disk (for example E:<\/code>) to use as the backup target \u2014 backing up to a folder on the same volume you are protecting defeats the purpose, because a failed disk or a ransomware run takes the backups with it.<\/p>\n\n\n\nHow VSS Makes Backups Consistent<\/h2>\n\n\n\n
vssadmin list writers | Select-String -Pattern \"Writer name|State\"<\/code><\/pre>\n\n\n\nState: [1] Stable<\/code>. A writer stuck in Failed<\/code> or Retryable<\/code> means that application’s data will not be captured correctly \u2014 fix the application first (usually by restarting its VSS writer service) before trusting the backup schedule.<\/p>\n\n\n\nSchedule a Full Server Backup with System State<\/h2>\n\n\n\n
wbadmin<\/code> captures the OS volume, your data volume, and the system state (registry, AD database, boot files) needed to rebuild the server. Run this once from an elevated prompt:<\/p>\n\n\n\nwbadmin enable backup -addtarget:E: -schedule:02:00 `\n -include:C:,D: -systemState -quiet<\/code><\/pre>\n\n\n\nwbadmin delete backup -backupTarget:E: -keepVersions:7 -quiet<\/code> from a scheduled task. For databases, prefer the application’s native backup (for example, SQL Server’s own BACKUP DATABASE<\/code> jobs) and use the Windows-level backup as the safety net \u2014 the two layers protect against different failure modes.<\/p>\n\n\n\nTake One-Time Backups and VSS Snapshots<\/h2>\n\n\n\n
vssadmin create shadow \/for=C:\nwbadmin start backup -backupTarget:E: -include:C: -systemState -quiet<\/code><\/pre>\n\n\n\nvssadmin<\/code> snapshot is nearly instant and is ideal as a pre-change rollback point, while wbadmin<\/code> produces the restorable backup set. Many providers also offer scheduled hypervisor-level snapshots of the whole VM; treat those as an extra layer, not a replacement, because a snapshot stored on the same storage array as the VM disappears with it.<\/p>\n\n\n\nCopy Backups Offsite with Robocopy<\/h2>\n\n\n\n
robocopy E:\\WindowsImageBackup \\backup01\\offsiteps1 \/MIR `\n \/R:2 \/W:5 \/LOG:C:\\logs\\offsite-copy.log\nif %ERRORLEVEL% LEQ 7 (echo Offsite copy OK) else (echo Offsite copy FAILED)<\/code><\/pre>\n\n\n\n\/MIR<\/code> flag plus a small retention script gives you that for free. Encrypt the offsite target (BitLocker on the destination volume, or the provider’s server-side encryption) since the backup set contains your data in cleartext.<\/p>\n\n\n\nVerify and Test Restores<\/h2>\n\n\n\n
wbadmin get versions -backupTarget:E:\nwbadmin start recovery -version:06\/01\/2026-02:00 `\n -itemType:File -items:C:\\data -recoveryTarget:F:\restore-test -quiet<\/code><\/pre>\n\n\n\nrobocopy \/L<\/code> lists what would change). Record the test date and result next to your runbook so the plan stays honest.<\/p>\n\n\n\nSummary<\/h2>\n\n\n\n