*Cube-Host– full cloud services!!
*Cube-Host– full cloud services!!
Automated backups are the simplest way to protect a Windows VPS from accidental deletion, ransomware, failed updates, or disk corruption. In this guide you’ll set up Windows Server Backup (WSB), automate wbadmin runs with Task Scheduler, keep multiple versions with date-based folders, and add quick file-level snapshots with Robocopy and VSS.
For predictable backup jobs and stable disk throughput, choose a reliable Windows VPS with enough storage and I/O performance to store and transfer backup sets.
Rule #1: don’t store backups only on the same disk as the system. If the VPS is compromised or the disk fails, you lose both server and backup.
Windows Server Backup is a built-in feature for scheduled backups of volumes/files and (depending on the mode) system recovery components.
Install via PowerShell (Run as Administrator):
Install-WindowsFeature Windows-Server-Backup -IncludeManagementToolsVerify installation:
Get-WindowsFeature Windows-Server-Backup
For network storage, create a dedicated directory and grant Read/Write only to SYSTEM, Administrators (or Domain Admins), and (if needed) the backup account/computer object.
Important: the Windows Server Backup GUI wizard has a limitation for network targets: it typically keeps only one “current” copy. To keep multiple versions on a network share, use wbadmin with date-based folders (next section) and rotate old folders yourself.
This approach creates a folder like \\backup-srv\win-vps01\YYYY-MM-DD\ and writes a backup there. This is the simplest way to keep many versions on a network share.
Create a folder for scripts, for example C:\Scripts, and create a PowerShell file:
New-Item -ItemType Directory -Path C:\Scripts -Force
notepad C:\Scripts\WSB-DailyBackup.ps1Example script (edit paths and volumes to match your VPS):
$ErrorActionPreference = "Stop"
# Base path for backups (network share or secondary disk)
# Examples:
# $Base = "\\NAS01\Backups\winvps01"
# $Base = "D:\Backups\winvps01"
$Base = "\\BACKUP-SERVER\Backups\winvps01"
$Date = Get-Date -Format "yyyy-MM-dd"
$Target = Join-Path $Base $Date
New-Item -ItemType Directory -Path $Target -Force | Out-Null
# Log file
$LogDir = "C:\Windows\Logs"
$Log = Join-Path $LogDir ("WSB-" + $Date + ".log")
"=== START: $(Get-Date) ===" | Out-File -FilePath $Log -Append
# Full backup of critical volumes + system recovery components
# -allCritical includes volumes required to recover Windows (typical baseline)
# Add -include:D: if you want additional data volumes.
wbadmin start backup -backupTarget:$Target -allCritical -quiet 2>&1 | Out-File -FilePath $Log -Append
"=== END: $(Get-Date) ===" | Out-File -FilePath $Log -AppendLogs: you can also inspect WSB logs in C:\Windows\Logs\WindowsServerBackup\*.log.
If you back up to a locally attached disk and want to limit versions using WSB itself:
# Keep only N versions (example: 14)
wbadmin delete backup -keepVersions:14 -quietOpen taskschd.msc → Create Task… → run as SYSTEM + Run with highest privileges. Add a daily trigger and an action:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\Scripts\WSB-DailyBackup.ps1
Create a scheduled task that runs daily at 03:00 as SYSTEM with highest privileges:
schtasks /Create /TN "WSB Daily Backup" ^
/TR "powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\Scripts\WSB-DailyBackup.ps1" ^
/SC DAILY /ST 03:00 /RU "SYSTEM" /RL HIGHEST /FCheck last run result:
schtasks /Query /TN "WSB Daily Backup" /V /FO LISTFor file-heavy data (websites, uploads, documents), Robocopy snapshots can be faster than full system backups and easier to restore at file level.
Example PowerShell snippet (create a dated folder and copy files):
$Base = "\\BACKUP-SERVER\Backups\winvps01-files"
$Date = Get-Date -Format "yyyy-MM-dd"
$Dest = Join-Path $Base $Date
New-Item -ItemType Directory -Path $Dest -Force | Out-Null
# Example: copy website data
robocopy "C:\inetpub\wwwroot" $Dest /E /Z /R:2 /W:5 /COPY:DAT /DCOPY:T /XJ /LOG+:("C:\Windows\Logs\Robocopy-" + $Date + ".log")Note: avoid /MIR unless you fully understand that it can delete files in the destination to match the source.
Shadow copies provide “previous versions” and help restore individual files quickly. They are useful for quick rollback, but they are not a replacement for offsite backups because they usually live on the same storage.
Reserve 10–20% of the disk for shadow copies (example for C:):
vssadmin add shadowstorage /for=C: /on=C: /maxsize=20%
Create a snapshot (example) and list snapshots:
wmic shadowcopy call create Volume="C:\\"
vssadmin list shadows
To access a snapshot, you can create a read-only directory link to the shadow copy device path (run as Administrator). Replace HarddiskVolumeShadowCopyX with the correct ID from vssadmin list shadows:
mklink /d C:\ShadowCopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyX\
After copying the required files, remove the link:
rmdir C:\ShadowCopyC:\Windows\Logs\WindowsServerBackup\ and your script logs.Example rotation for date folders (keep last 30 days):
$Base = "\\BACKUP-SERVER\Backups\winvps01"
$KeepDays = 30
Get-ChildItem $Base -Directory | Where-Object {
$_.Name -match '^\d{4}-\d{2}-\d{2}$' -and $_.CreationTime -lt (Get-Date).AddDays(-$KeepDays)
} | Remove-Item -Recurse -Forcewbadmin + date-based folders and your own rotation.-ExecutionPolicy Bypass.A production-ready Windows VPS backup strategy usually combines: scheduled system/volume backups (WSB/wbadmin), offsite storage, clear logging, retention rotation, and periodic restore tests. Add Robocopy snapshots for fast file restores and VSS for quick rollback — but always keep at least one copy outside the VPS.
Need stable disk I/O, enough space for retention, and predictable backup performance? Order a reliable Windows VPS and automate backups from day one using the workflow above.
