Hjälpcentral

Windows Server includes a built-in backup feature capable of full-server, volume-level, or file-level backups on a schedule — without requiring third-party software for basic protection.

Prerequisites

• Windows Server VPS with Administrator access
• A destination for backups (a separate volume, network share, or attached storage)

Step 1 — Install Windows Server Backup

Install-WindowsFeature Windows-Server-Backup

Step 2 — Open Windows Server Backup

wbadmin

Or via GUI: search "Windows Server Backup" in the Start menu.

Step 3 — Run a One-Time Backup (Testing)

wbadmin start backup -backupTarget:E: -include:C: -allCritical -quiet

Replace E: with your actual backup destination drive.

Step 4 — Schedule Automated Backups

wbadmin enable backup -addtarget:E: -schedule:02:00 -include:C: -allCritical -quiet

This schedules a daily backup at 2:00 AM to drive E:.

Step 5 — Verify the Schedule

wbadmin get status

Backing Up Specific Folders Only (Not Full System)

For application-specific data rather than a full system backup, use robocopy in a scheduled task instead:

robocopy C:\inetpub\wwwroot E:\Backups\www /E /Z /LOG:E:\Backups\backup.log

Schedule it:

$action = New-ScheduledTaskAction -Execute "robocopy.exe" -Argument "C:\inetpub\wwwroot E:\Backups\www /E /Z"
$trigger = New-ScheduledTaskTrigger -Daily -At 2am
Register-ScheduledTask -Action $action -Trigger $trigger -TaskName "Daily File Backup" -RunLevel Highest

Backing Up SQL Server Databases

BACKUP DATABASE MyApp TO DISK = 'E:\Backups\MyApp.bak' WITH FORMAT;

Automate this via SQL Server Agent (available in non-Express editions), or a scheduled PowerShell script calling sqlcmd.

Copying Backups Off-Server (Critical for Real Disaster Recovery)

A backup stored only on the same physical VPS provides limited protection. Transfer copies elsewhere — via SFTP to another server, or to cloud storage:

robocopy E:\Backups \\REMOTE_SERVER\Backups /E /Z

Restoring from a Backup

wbadmin get versions
wbadmin start recovery -version:VERSION_IDENTIFIER -itemtype:Volume -items:C:

Full recovery typically requires booting from Windows Recovery Environment for a complete system restore.

Testing Your Backups (Not Optional)

Periodically verify backup integrity by restoring specific files or a test database to confirm the backup is actually usable, not just "completed successfully."

Common Errors

"The backup destination volume is not eligible" — the target drive can't be the same volume being backed up; use a separate disk.

Scheduled backup didn't run — verify the Windows Server Backup service is running and check Event Viewer under Applications and Services Logs for backup-specific errors.

Best Practices

• Follow the 3-2-1 rule: 3 copies, 2 different media, 1 off-site
• Schedule backups during low-traffic hours
• Test restores periodically, not just backup completion
• Also check whether your VPS provider offers snapshot functionality as an additional recovery option

Related Articles

• Windows Server Security Checklist for a New VPS
• How to Install SQL Server on a Windows VPS
• How to Transfer Files To and From a Windows VPS