WBADMIN Command Guide | Windows Server Backup & Recovery (2026)

The wbadmin command is a powerful Windows command-line utility used to manage the Windows Server Backup feature. It allows administrators to create and manage backups of the operating system, individual volumes, files, folders, and applications from a standard command prompt or terminal. While many users are familiar with the graphical user interface (GUI) of Windows Server Backup, wbadmin provides the scriptability and granular control necessary for enterprise-grade automation and disaster recovery.

In modern IT environments, where server uptime is critical, wbadmin is an essential tool for creating "Bare Metal" recovery images, backing up the System State, and managing backup storage efficiently. It is available on Windows Server versions from 2008 onwards and on desktop versions of Windows (Vista and later), though some functionality varies between desktop and server editions.

This ultimate guide for 2026 covers everything from basic syntax to advanced multi-volume backup strategies. We will explore more than 10 practical examples, detailed troubleshooting steps for "Access Denied" or "VSS" errors, and how to use wbadmin in your daily administration workflows to ensure data integrity.

What Is the Wbadmin Command?

The wbadmin command (Windows Backup Admin) is the command-line interface for the Windows Server Backup (WSB) feature. It replaces the legacy ntbackup tool found in even older versions of Windows. Unlike its predecessor, wbadmin is built on the Volume Shadow Copy Service (VSS) architecture, ensuring that even open files can be backed up reliably without interrupting running services.

Key Capabilities of Wbadmin:

Full Volume Backups: Back up entire drives (C:, D:, etc.) to local or network targets.
System State Backups: Capture the registry, boot files, Active Directory, and other critical system components.
Bare Metal Recovery (BMR): Create images that allow you to restore a server from scratch to new hardware.
Backup Management: Query existing backups, delete old ones, and check the status of running jobs.
Scriptability: Integrate backups into scheduled tasks or custom maintenance scripts.

Syntax

The syntax for wbadmin is modular, consisting of various subcommands followed by parameters.

wbadmin <command> <parameters>

Common Subcommands

start backup: Runs a one-time backup job.
stop job: Stops a currently running backup or recovery job.
get versions: Lists backups available for recovery.
get items: Lists files/folders in a specific backup.
get status: Shows the status of the current operation.
delete backup: Removes old or redundant backups to free up space.
enable backup: Configures or updates a daily backup schedule.

Detailed Parameters and Switches

Parameters for `start backup`

Switch	Description
`-backupTarget`	Specifies the location for the backup (e.g., `E:` or `\\Server\Share`).
`-include`	A comma-separated list of volumes or files to include in the backup.
`-allCritical`	Automatically includes all volumes required for a full system recovery (Bare Metal).
`-systemState`	Backs up the system state data (Registry, AD, etc.).
`-noInheritAcl`	Prevents the backup from inheriting the ACL (Access Control List) of the target.
`-quiet`	Runs the command without prompting for user confirmation.
`-vssFull`	Performs a full VSS backup (clears log files of applications like Exchange).
`-vssCopy`	Performs a VSS copy backup (does not clear log files).

10 Practical Wbadmin Command Examples

1. Simple Volume Backup

To back up your system drive (C:) to an external drive (E:):

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

Explanation: This is the most basic backup. The -quiet flag ensures the process runs without asking "Are you sure?".

2. Full Bare Metal Recovery Backup

For a complete system recovery including the OS and all critical files:

wbadmin start backup -backupTarget:F: -allCritical -vssFull -quiet

Explanation: Using -allCritical is the best practice for ensuring a server can be restored to different hardware if the original fails.

3. System State Backup

If you only need the core registry and configuration (useful for domain controllers):

wbadmin start systemstatebackup -backupTarget:D: -quiet

Expect Output: Starting the backup operation... successfully completed. Explanation: Essential for Active Directory maintenance or before making major configuration changes.

4. Backing Up Multiple Volumes

You can comma-separate volumes for a single backup job.

wbadmin start backup -backupTarget:G: -include:C:,D:,E: -quiet

Explanation: This consolidates multiple local drives into one backup archive on drive G:.

5. Backup to a Network Share

For enterprise environments with centralized storage:

wbadmin start backup -backupTarget:\\BackupServer\Archive -include:C: -user:AdminName -password:SecretPassword -quiet

Warning: Ensure the network path is accessible and the user has full read/write permissions.

6. Listing Available Backups

To see what historical backups you can restore:

wbadmin get versions -backupTarget:E:

Explanation: This returns a list of "Version identifiers" (timestamps) which are required for recovery operations.

7. Checking Current Backup Status

If a backup was scheduled but you aren't sure if it's finished:

wbadmin get status

Explanation: Provides a progress percentage and the current file being processed.

8. Deleting Old Backups (Maintenance)

To free up space on your backup target:

wbadmin delete backup -version:03/25/2026-10:00 -quiet

Explanation: Deletes a specific backup version identified by its timestamp. You can also use -keepVersions:5 to keep only the 5 most recent backups.

9. Restoring the System State

In a disaster recovery scenario (usually from Safe Mode or DSRM):

wbadmin start systemstaterecovery -version:03/20/2026-14:00 -backupTarget:E: -quiet

Explanation: This initiates the process of rolling back the system state to the specified date.

10. Scheduling a Daily Backup

To automate your protection with a recurring task:

wbadmin enable backup -addtarget:E: -schedule:03:00 -include:C:,D: -allCritical

Explanation: Sets up a daily job that runs at 3:00 AM, protecting all critical system volumes.

Common Use Cases for Wbadmin

1. Active Directory Disaster Recovery

Domain administrators use wbadmin start systemstatebackup regularly to ensure the AD database (NTDS.dit) can be restored in case of database corruption or accidental object deletion.

2. SQL Server Configuration Backup

While SQL databases should be backed up using SQL-specific tools, the underlying OS configuration and non-SQL volumes are often protected via wbadmin to ensure the server environment can be rebuilt quickly.

3. Bare Metal Server Migrations

When moving from a physical server to a virtual machine (P2V) or to new server hardware, wbadmin -allCritical creates the necessary image for the Windows Recovery Environment (WinRE) to complete the migration.

4. Patching Pre-Verification

Before applying major Windows Updates or service packs, running a quick backup ensures a "point in time" snapshot is available if the update causes a Blue Screen of Death (BSOD).

Troubleshooting Common Issues

Issue 1: "Access Denied" (Error 0x80070005)

Cause: Attempting to run wbadmin from a standard shell without administrator rights. Solution: Open an "Elevated" Command Prompt by right-clicking and selecting "Run as administrator."

Issue 2: "The Backup target is not reachable"

Cause: Network issues, incorrect share path, or the target drive is disconnected. Solution: Verify the path with dir \\Server\Share and ensure the target disk is online in diskpart.

Issue 3: "A Volume Shadow Copy Service (VSS) operation failed"

Cause: A conflict with another backup tool or the VSS service is disabled/stuck. Solution: Check the status of VSS writers using vssadmin list writers. Restart the "Volume Shadow Copy" service if necessary.

Issue 4: "The backup destination is not valid"

Cause: You are trying to back up a volume to itself, or the target is a formatted partition that wbadmin doesn't recognize. Solution: Ensure the backup target is a dedicated disk or a correctly shared network folder.

Related Commands

VSSADMIN – VSS Manager

wbadmin relies on VSS. Use vssadmin to manage shadow storage and check for healthy VSS writers.

DISKPART – Partition Manager

Before running wbadmin, use diskpart to ensure your backup target disks are properly initialized and online.

SFC – System File Checker

If your system state backup is failing due to file corruption, run sfc /scannow to repair base OS files before attempting the backup again.

Tips and Best Practices

Validate Your Backups: Occasionally run wbadmin get items to ensure the backup contains the files you expect.
Dedicated Backup Drives: For local backups, use a dedicated physical disk rather than a partition on the system disk.
Rotate Your Medias: If using USB drives, rotate them weekly and keep one offsite for protection against fire or theft.
Monitor the Event Viewer: Check Applications and Services Logs -> Microsoft -> Windows -> Backup for detailed error logs if a job fails.
Use the -quiet Flag in Scripts: This prevents the command from hanging while waiting for a user input that will never come.
Avoid Triggers on the Same Schedule: Ensure multiple backup jobs (like file-level and system-state) do not overlap, as they may conflict for VSS resources.
Include BCD Data: Always use -allCritical if your goal is to be able to boot the machine after a restore.
Check Space Requirements: A full backup usually requires space equal to 50-70% of the used data on the source volumes due to VSS compression.
Network Share Permissions: Use a dedicated service account for network backups to improve security and auditing.
Test Your Restore Procedure: A backup is only as good as your ability to restore it. Periodically test restorations on non-production hardware.

Frequently Asked Questions

Can I run wbadmin on Windows 10/11 Home?

No, the Windows Backup feature (and thus wbadmin) is restricted to the Pro, Enterprise, and Server editions of Windows.

Is wbadmin better than third-party tools?

wbadmin is highly integrated and free, making it great for "Bare Metal" recovery. Third-party tools often offer better compression, encryption, and central management dashboards but may come at a cost.

How do I stop a stuck backup job?

Run wbadmin stop job in an elevated command prompt. This will safely terminate the VSS sessions and release the locked files.

Does wbadmin encrypt backups?

No, wbadmin does not provide native encryption. If security is a concern, you should back up to a BitLocker-encrypted volume or a secure network location.

What is the difference between VSS Full and VSS Copy?

VSS Full notifies applications that a backup occurred and allows them to truncate their log files (common for Exchange and SQL). VSS Copy creates the backup without notifying the applications or clearing logs.

Can I back up to a mapped drive?

No, wbadmin typically does not support mapped drive letters (like Z:). Always use the full UNC path (\\Server\Share).

Why is my wbadmin backup getting slower over time?

This often happens if you are saving to the same disk repeatedly and it is becoming fragmented, or if the VSS shadow storage is reaching its capacity.

Can I restore a backup from a newer version of Windows to an older one?

No, typically you can only restore backups to the same or a newer version of the operating system.

Quick Reference Card

Goal	Command Pattern
Full Backup (Bare Metal)	`wbadmin start backup -backupTarget:E: -allCritical -quiet`
System State Only	`wbadmin start systemstatebackup -backupTarget:D:`
Check Status	`wbadmin get status`
List Backups	`wbadmin get versions -backupTarget:E:`
Delete Old Backups	`wbadmin delete backup -keepVersions:10`
Stop Running Job	`wbadmin stop job`

Summary

The wbadmin command remains a cornerstone of Windows Server administration and professional disaster recovery planning in 2026. Its ability to create full-metal images, system-state snapshots, and automated schedules directly from the command line makes it superior for automation compared to the GUI.

By following the examples and best practices in this guide, you can establish a robust backup strategy that protects your critical data and ensures your infrastructure can recover from hardware failure, software corruption, or security breaches. Remember: the most expensive backup is the one you didn't take.