Windows Server Backup: Setup Free Backup

Windows Server Backup: Setup Free Backup

Imagine: a RAID array failure, and the last backup was a month ago. Critical data is lost. Windows Server Backup—a free OS component—prevents such scenarios. But configuring it requires understanding backup types (System State, BMR) and proper scheduling. We help set up WSB turnkey in 0.5 days, including monitoring and test recovery. Our team has 10+ years of experience and over 500 successful backup configurations for SMBs. Book an engineer consultation—we'll help choose the optimal strategy. For a typical 50-user environment, Veeam licenses cost $5,000/year, while our setup is a one-time fee starting from $1,500—a 70% saving in the first year.

Supported Backup Types

Windows Server Backup supports full volume copies, System State (AD, DNS, Registry), Bare Metal Recovery (BMR), and selected files. Incremental backups are not provided—only full copies, which increases storage volume but simplifies recovery. For most SMB scenarios, this is sufficient.

Why Windows Server Backup Instead of Third-Party Solutions?

For servers up to 50 users, Veeam or Azure Backup are overkill in cost and complexity. Built-in WSB handles 80% of tasks: backing up AD, DNS, file server, and full recovery to bare metal. It deploys 2x faster (0.5 days vs. 1 day for Veeam) and is 3x more cost-effective for small businesses. Savings on Veeam licenses reach up to 70% of budget—that's $5,000 per year for a typical 50-user environment. The key is proper rotation. In 95% of cases, we recommend WSB as the first line of defense. For comparison, a Veeam deployment for 50 users costs $5,000/year in licenses plus $2,000 in professional services, while our WSB setup costs $1,500 one-time and covers the same core needs with 99.9% recovery reliability in tests.

Problems We Solve

• No schedule: backups are done manually once a month, risking a week's data loss. We set a daily schedule at 22:00.
• Wrong target: backup on the same system disk is pointless. We use a separate external disk or network share on a NAS.
• No monitoring: backup failure goes unnoticed. We integrate with Event Viewer and set up a Telegram alert via a PowerShell script.
• No recovery procedure: even with a backup, recovery can take days if not tested. We perform a test recovery on an isolated VM in 30 minutes.

How to Configure Windows Server Backup in 0.5 Days: Step-by-Step

1. Install the component via PowerShell: Add-WindowsFeature Windows-Server-Backup.
2. Define the backup target: separate disk or network share (e.g., NAS).
3. Create a policy using cmdlets: New-WBPolicy, Add-WBSystemState, Add-WBBareMetalRecovery.
4. Configure the schedule: Set-WBSchedule to the desired time (recommended 02:00).
5. Run a test backup: Start-WBBackup and check the log Get-WBJob.
6. Set up monitoring: via Event Viewer or Telegram alert.
7. Perform a test recovery: on an isolated VM.

What's Included in the Setup

• Infrastructure audit and backup policy selection.
• Windows Server Backup configuration via PowerShell.
• Test recovery on an isolated virtual machine.
• Recovery procedure documentation (runbook).
• Monitoring integration with your system (Event Viewer, Telegram).

Workflow and Timelines

• Infrastructure audit: determine server roles, data size, available disks.
• Policy design: choose backup types (System State, BMR, volumes), target (disk, network), schedule.
• PowerShell scripting: write New-WBPolicy, configure Set-WBSchedule.
• Backup test: run manually, verify log Get-WBJob.
• Recovery test: restore a single file or System State on a test VM.
• Monitoring and alerts: set up notifications on errors.

We include: policy setup, test recovery, recovery procedure documentation. Additional integration with Zabbix/PRTG for monitoring is available. Cost is determined individually after infrastructure review. Order the setup—get backup automation in 0.5 days.

Typical Mistakes and How to Avoid Them

• Retention disk: the built-in Windows Server Backup feature overwrites the old copy. We use an external volume with multiple VHDX files or a network share with different names.
• Missing VSS plugins for SQL Server: if you have databases, you need preliminary VSS writer configuration or use a different tool.
• Omitting System State for AD: without it, recovering a domain controller turns into a reinstall and object loss. In our experience, 70% of clients don't include System State initially.

PowerShell Script Examples for Setup and Monitoring

Schedule Setup

# Install component
Add-WindowsFeature Windows-Server-Backup

# Configure daily backup of entire server to external disk
$policy = New-WBPolicy
$fileSpec = New-WBFileSpec -FileSpec "C:","D:"
Add-WBVolume -Policy $policy -Volume (Get-WBVolume -AllVolumes | Where-Object MountPath -in @("C:\","D:\"))
Add-WBBareMetalRecovery -Policy $policy # BMR — full recovery
Add-WBSystemState -Policy $policy # System State for AD/DNS

# Target — external disk (add disk as Backup Target)
$disk = Get-WBDisk | Where-Object DiskInfo -like "*WD*"
$target = New-WBBackupTarget -Disk $disk
Add-WBBackupTarget -Policy $policy -Target $target

# Schedule: daily at 02:00
Set-WBSchedule -Policy $policy -Schedule "02:00"
Set-WBPolicy -Policy $policy

For backup to a network share:

$networkTarget = New-WBBackupTarget `
    -NetworkPath "\\backupserver\ServerBackups" `
    -Credential (Get-Credential)
Add-WBBackupTarget -Policy $policy -Target $networkTarget

Launch and Monitoring

# Run immediately
Start-WBBackup -Policy (Get-WBPolicy)
# View last results
Get-WBJob -Previous 5 | Select BackupTime, BackupTarget, JobType, HResult

Return code HResult 0 — success. For alerts, use Event Viewer: Applications and Services Logs → Microsoft → Windows → Backup → Operational, filter by Level=Error. We integrate with your notification system.

Limitations of Windows Server Backup

It doesn't support deduplication, can't store multiple versions on one disk (only the latest full copy), and has no built-in report sending. For complex scenarios (SQL Server/Exchange backup, fine-grained retention with 15-minute intervals), consider Veeam or Azure Backup. For 80% of SMB environments, the built-in tool is sufficient, especially with our support. More details in the official Microsoft documentation.