Windows Server 2025 / How to Create and Verify a Windows Server Backup
Windows Server Backup protects selected files, volumes, or system state. Decide the recovery objective first, use a location separate from the source, and verify stored versions and an actual restore rather than relying only on a success message.
Match backup scope to recovery needs
| Need | Scope to consider |
|---|---|
| Deleted individual file | File, folder, or containing data volume |
| OS and boot recovery | Bare metal recovery including critical volumes |
| Role such as a domain controller | Role-appropriate system-state and recovery plan |
| Business database | Application-supported consistent backup |
Recovery Point Objective (RPO) defines acceptable data loss; Recovery Time Objective (RTO) defines acceptable restoration time. A completed backup may still miss the required recovery if scope and timing were never defined. File copies and VM checkpoints do not automatically satisfy every objective. This lab begins with a small FS1 folder, not controller recovery.
Prepare separate backup storage and a test file
Use a new backup disk or volume, represented as E:, separate from source D:. Two VHDX files on one host can demonstrate procedure without surviving that host’s storage failure.
Install-WindowsFeature Windows-Server-Backup Get-Volume -DriveLetter D,E | Select-Object DriveLetter,FileSystemLabel,SizeRemaining New-Item -ItemType Directory -Path 'D:\BackupLab' 'backup version A' | Set-Content -LiteralPath 'D:\BackupLab\sample.txt' -Encoding UTF8 Get-FileHash -LiteralPath 'D:\BackupLab\sample.txt' -Algorithm SHA256
Create BackupLab and sample.txt only if absent. Do not overwrite an existing file; choose a new test name if needed. Record the original contents and SHA-256 hash and verify backup target capacity and access.
Run a one-time folder backup
- Open wbadmin.msc and select Local Backup → Backup Once.
- Choose different options and a custom selection containing D:\BackupLab.
- Select the prepared E: destination, checking source versus target.
- Review Volume Shadow Copy Service (VSS) options and confirmation.
- Run and record completion, time, destination, included items, and relevant events.
Use this elevated-command alternative only if not already using the GUI. It retains confirmation prompts:
wbadmin start backup -backupTarget:E: -include:D:\BackupLab -vssCopy
Review wbadmin backup parameters. VSS helps supported applications produce consistent backups. Switching to -vssFull without considering other backup products can affect log and incremental strategies. Do not infer consistency for unsupported applications.
Inspect stored versions and recoverable scope
wbadmin get versions -backupTarget:E:
Use backup version queries to inspect actual target storage, version identifiers, time, and recovery types. A local catalog entry without an available storage device is not enough.
Repeated backups to the same network-share destination can overwrite the prior backup. Check target-specific retention and space instead of assuming version history. Do not rearrange the backup’s internal folder structure or move only some files.
Plan schedules, retention, and restore tests together
Only after a successful backup and restore test, configure Backup Schedule with the required time, scope, and destination. A dedicated-disk setup can format or change normal access to the target, so do not select a disk containing needed files.
- Monitor failed and missed runs and assign an owner.
- Calculate storage for required recovery points and retention.
- Protect backups from compromise of the source server’s administrative account.
- Restore to a separate location and record contents, permissions, and duration.
Stopping a schedule or removing the feature does not necessarily clean up old backups. Verify retention and usable versions before deleting storage. Keep this lab backup for the restore exercise.
