Never Lose Your Data Again: Windows Server Backup Setup, Schedule and Restore

Windows Server Backup is the free built-in backup feature of Windows Server, and it saves the full server, the system state, volumes or single files to a disk or a network share. A disk dies on a Monday? That’s the day Windows Server Backup earns its keep. Someone deletes the wrong folder on a Friday evening. Windows Server Backup is the free feature that turns either one into an annoying morning. No extra license needed.

• Add the feature: one PowerShell line.
• A dedicated disk beats a NAS share.
• Schedule it daily in the wizard.
• One copy offline or off site.
• Test a restore now and then.

It’s built into every Windows Server release. It backs up files, volumes, system state and whole servers for bare metal recovery.

It runs on a schedule or on demand, and it restores through a wizard or with wbadmin.

Small offices with one server are exactly where it shines. For a single server with a dedicated backup disk, it’s still the first tool we’d set up, before anything goes into production.

What Windows Server Backup is

WSB, for short, is Microsoft’s built-in backup and recovery feature for the server, at no extra cost.

It uses the Volume Shadow Copy Service to take consistent block-level backups of running servers.

It can restore single files, folders, volumes, applications, system state or the entire server to other hardware.

You drive it from a console, with wbadmin commands or with PowerShell cmdlets.

It protects against the everyday disasters.

• A failed disk.
• An accidental deletion.
• A bad update.
• Corrupted software.
• Ransomware, if you keep an offline copy.

It’s a solid choice for one or a few servers. It isn’t a central backup platform.

Larger estates usually combine it with a dedicated product or a cloud service, or replace it.

There’s also no deduplicated long-term retention.

How to install Windows Server Backup

You add the feature in Server Manager, or with one PowerShell command run as administrator. No restart is needed.

1. Open Server Manager and select Manage, then Add Roles and Features.
2. Choose Role-based or feature-based installation and select the server.
3. Skip the Server Roles page. On Features, tick Windows Server Backup.
4. Select Install and wait for it to finish.

PowerShell is handy on Server Core, where the console isn’t available locally:

Install-WindowsFeature Windows-Server-Backup

On Server Core you manage backups with wbadmin or the WindowsServerBackup PowerShell module.

Remote management works too. In the console on another server, choose Action, Connect to Another Server.

Where to store backups

For scheduled backups, we’d pick a disk dedicated to them, internal or USB.

Windows formats it, hides it from Explorer and keeps many restore points. It deletes the oldest when the disk fills.

A volume or a network share works too, with limits. For real protection, add at least one off-site or offline copy.

Microsoft’s own documentation for wbadmin warns about the network share limit directly.

A backup saved to a remote shared folder is overwritten when the same computer backs up to that folder again.

If a NAS is your only target, create a fresh folder per run with a script. Or use the NAS’s own snapshots.

The classic 3-2-1 rule still fits: three copies of the data, on two kinds of media, one of them off site.

To size the disks, our RAID calculator helps you work out usable capacity on a backup array.

We’d make the dedicated backup disk at least 1.5 times the size of the data you back up. That typically leaves room for a few weeks of daily versions on a typical file server.

Your first Windows Server backup

Run one manual full backup before you set a schedule. The first run copies every used block, so it generally takes the longest.

Later runs only copy changes.

• Open the console and select Local Backup.
• In the Actions pane, select Backup Once.
• Choose Different options and select Next. The other choice reuses the scheduled settings.
• Choose Full server, which is recommended, or Custom to pick items.
• Choose Local drives or Remote shared folder and select the target.
• Select Backup, then watch the progress. Closing the window doesn’t stop the job.

Under Custom you can pick bare metal recovery, system state, volumes, or files and folders.

Two settings on the Custom path are often overlooked.

If WSB is your only backup for that application, pick the full option.

When the job ends, check the result in the console’s Messages list. Event Viewer has it too, under Applications and Services Logs, Microsoft, Windows, Backup.

Scheduling automatic Windows Server backups

Use the Backup Schedule wizard in the console. After that, Windows runs the backup through Task Scheduler with no one logged on.

Daily is the minimum for most business servers.

• In the console, select Backup Schedule in the Actions pane.
• Choose Full server or Custom items.
• Set the time. Once a day at a chosen hour, or More than once a day by adding several times, in 30-minute steps.
• Choose the destination: a hard disk dedicated to backups, a volume, or a shared network folder.
• For a dedicated disk, select it and confirm that it will be formatted. Tick Show All Available Disks if it’s missing.
• Review and select Finish.

How often should it run? That follows from your recovery point objective: how much work you can afford to lose.

Several runs a day are cheap, because each one only copies changed blocks.

How long backups are kept

On a dedicated backup disk, the tool keeps as many versions as fit. It deletes the oldest automatically when it needs space.

There’s no setting for “keep 30 days”. On a network share, only the latest version exists.

If you need fixed retention, such as monthly copies for a year, rotate extra disks or add another backup product.

Full or incremental

The tool doesn’t ask you to plan full and incremental jobs by hand. You choose under Configure Performance Settings.

Either way, every version on the disk restores as a complete point in time.

Backup types: full server, system state, volumes, files

Most single-server setups simply schedule a full server backup every day.

A practical plan for a small business has three parts.

• A daily full server backup to a dedicated disk.
• A weekly copy to a second disk kept off site.
• A separate system state backup on domain controllers before any major change.

Restoring files, volumes or a whole server

Restores start from the Recover action in the console. You choose the backup date, then what to bring back.

A server that won’t boot is restored from installation media with System Image Recovery. We’d practise each type before you need it.

Files and folders

• Open the console and select Recover.
• Choose This server, or a backup stored elsewhere, and select the date and time.
• Choose Files and folders and browse to the items.
• Restore to the original location or, safer, to another folder. Decide what to do with existing copies.
• Keep the option for access control list permissions ticked, so file permissions come back too.

A volume

Choose Volumes in the Recovery Wizard, select the source volume and a destination volume, and confirm.

Everything on the destination is overwritten, so double-check the drive letter.

The system volume can’t be restored this way. That’s the job of bare metal recovery.

System state

Choose System state in the wizard, or use the wbadmin line from the table further down.

On a domain controller, start in Directory Services Restore Mode first. Then decide between two kinds of restore.

Restart when the restore finishes.

Bare metal recovery to other hardware

• Boot the server from Windows Server installation media of the same version.
• Select Next, then Repair your computer.
• Choose Troubleshoot, then System Image Recovery.
• Pick the latest image from the attached backup disk or a network location. Then follow the wizard, which repartitions the target disks.

We’d test a bare metal restore into a virtual machine at least once a year. That’s how you learn, on a quiet afternoon, that a storage driver is missing or the backup disk was the wrong one.

Automating Windows Server Backup with PowerShell

The WindowsServerBackup module creates a policy object. You add what to back up and where.

Then you either run it once with Start-WBBackup or save it as the schedule with Set-WBPolicy.

The older wbadmin command does the same from Command Prompt and in batch files. Both need an elevated session.

A one-time backup of a folder, system state and bare metal recovery data to drive E:

$policy = New-WBPolicy
Add-WBFileSpec -Policy $policy -FileSpec (New-WBFileSpec -FileSpec "D:\Shares")
Add-WBSystemState -Policy $policy
Add-WBBareMetalRecovery -Policy $policy
Add-WBBackupTarget -Policy $policy -Target (New-WBBackupTarget -VolumePath "E:")
Start-WBBackup -Policy $policy

A daily schedule at 02:00 and 13:00 looks like this:

$policy = New-WBPolicy
Add-WBFileSpec -Policy $policy -FileSpec (New-WBFileSpec -FileSpec "D:\Shares")
Add-WBBackupTarget -Policy $policy -Target (New-WBBackupTarget -VolumePath "E:")
Set-WBSchedule -Policy $policy -Schedule 02:00, 13:00
Set-WBPolicy -Policy $policy -Force

The schedule only takes effect after Set-WBPolicy. Many scripts online leave that step out.

For status and versions:

Get-WBSummary
Get-WBJob -Previous 1
wbadmin get versions

And the same backups with wbadmin:

wbadmin start backup -backupTarget:E: -include:C:,D: -allCritical -quiet
wbadmin start systemstatebackup -backupTarget:E: -quiet
wbadmin start systemstaterecovery

For alerts, attach a task in Task Scheduler to event ID 4, the success event. The failure events in the Backup log work the same way.

Or let your monitoring system read Get-WBSummary.

Without some alert, a backup can quietly fail for weeks. A typical trigger is nothing more dramatic than an unplugged USB disk.

Good practice in 2026

Back up daily to a dedicated disk and keep one copy offline or off site. Encrypt removable disks, monitor every job and test restores on a schedule.

The same goes before a domain join, or before a domain rename. Run Backup Once first.

For the oldest release in the version table, see what to plan for Windows Server 2016.

Common mistakes with server backups

• Scheduling to a NAS share and expecting several versions. Only the latest one is there.
• Leaving the only backup disk next to the server.
• Never trying a restore until the day it’s needed.
• Carrying an unencrypted USB disk out of the building.
• Writing a schedule in PowerShell and skipping the line that saves the policy.
• Running with no alert, so a failed job goes unseen for weeks.
• Restoring a volume onto the wrong drive letter.

Terms used on this page

Windows Server Backup service name and startup type

Jobs fail and the console says the service won’t start? Look at the engine behind the wizard first.

Manual is correct here. The service starts by itself when a job runs, then stops again. Switched to Disabled, or to a named account? Put it back to Manual and Local System, then restart it. Microsoft’s Best Practices Analyzer rules flag both settings, because other values can make backup jobs fail.

Want to check it from PowerShell? This line shows the state:

Get-Service wbengine

How to delete old Windows Server backups

On a dedicated disk, the feature cleans up by itself. Older versions get dropped when space runs short. Want control anyway? Use the WindowsServerBackup module.

Keep the three newest backups on a target and remove the rest:

$target = Get-WBBackupTarget -Policy (Get-WBPolicy)
Remove-WBBackupSet -BackupTarget $target -KeepVersions 3 -Force

Only the oldest one, no prompt:

Remove-WBBackupSet -BackupTarget $target -DeleteOldest -Force

The cmdlet clears the backup from the catalog on the target and from the local system catalog. Details sit on the Remove-WBBackupSet reference.

For system state backups, wbadmin has its own switch. It needs an elevated prompt and membership in Administrators or Backup Operators.

wbadmin delete systemstatebackup -keepVersions:3

Never delete the WindowsImageBackup folder by hand while a schedule points at the disk. The catalog then lists backups that no longer exist.

Common Windows Server Backup failures and fixes

A NAS share holds only one version

Nightly backups to a shared folder overwrite each other. Last week’s file? Gone. A dedicated disk keeps older versions, with the NAS as an extra copy.

Scheduled jobs fail for weeks unnoticed

The backup disk got unplugged, or its USB port went to something else. Every job fails quietly. An alert on the Backup log catches it the first night.

Bare metal restore can’t see the disks

Replacement hardware with a different storage controller stops the restore. The driver is missing. A test restore into a VM shows that early.

A PowerShell schedule never starts

The policy was built and never saved. One more line, Set-WBPolicy, fixes it.

Ransomware reached the attached backup disk

A disk that stays connected gets encrypted along with the server. A rotated disk kept off site stays clean. Restore from that one.

Windows Server versions these backup steps cover

The console and wizard pages look the same across these releases. Server Core installations use PowerShell, wbadmin or remote management.

For the full option list of the command-line tool, see Microsoft’s wbadmin enable backup reference.

Moving off an old server? Our Windows Server 2025 Standard key comes as a genuine license. So do the Windows Server 2022 Standard key and the 2019 Standard key. Delivery is instant to email.

Data loss rarely announces itself. Give the feature a dedicated disk and a schedule, and keep one copy somewhere else.

Then restore something every few months. That small routine is what saves the day.