Back Up System State of Windows Server 2016 DC with PowerShell

Updated 7 November 2026 · Standard formula, shown below

Yes, you can back up the system state of a Windows Server 2016 domain controller using PowerShell, and the most reliable method is to use the built-in wbadmin command within a PowerShell script. You enter the system state backup command with appropriate parameters, and PowerShell executes it and reports the result, allowing you to automate and schedule the backup. This article explains exactly how to do it, what the command does, and how to avoid common pitfalls.

Why System State Backup Matters on a Domain Controller

On a domain controller, the system state includes critical Active Directory components: the NTDS.dit database, the SYSVOL folder, registry, boot files, and the COM+ class registration database. Unlike a full server backup, a system state backup is designed to restore AD DS to a consistent state, which is essential for recovering from accidental object deletions, database corruption, or a failed update. Without it, you may need to re-promote the server, losing all domain changes made since the last backup. The system state backup is also the foundation for performing an authoritative or non-authoritative restore of Active Directory.

How to Back Up System State with PowerShell

PowerShell does not have a dedicated system-state backup cmdlet, so you use wbadmin (the Windows Server Backup command-line tool) inside a PowerShell script. Here are the steps:

Install the Windows Server Backup feature if not already present: Install-WindowsFeature Windows-Server-Backup (requires admin rights).
Run PowerShell as Administrator.
Execute the backup command: wbadmin start systemstatebackup -backupTarget:E: -quiet (replace E: with your destination drive).
To verify, check the last backup time: wbadmin get versions.

For a more robust script, you can wrap this in a PowerShell function that logs the output and sends a notification. For example:

$backupResult = wbadmin start systemstatebackup -backupTarget:E: -quiet 2>&1
Write-Output $backupResult

You can also use Start-WBSystemStateBackup if you have the Windows Server Backup module loaded, but that cmdlet requires importing the module and may not be available in all environments by default.

Choosing a Backup Destination

The destination for a system state backup must be a local drive or a network share, but not the same disk that holds the system state (to avoid losing both in a disk failure). Common choices include:

A dedicated internal volume (e.g., D:)
An external USB drive (must be NTFS)
A network shared folder (e.g., \\server\backup)

When using a network share, you must provide credentials: wbadmin start systemstatebackup -backupTarget:\\server\share -user:DOMAIN\user -password:****. Note that wbadmin does not support backing up to a network share in some older versions, but Windows Server 2016 does support it for system state. However, using a local disk is faster and more reliable for a domain controller.

Common Problems and How to Avoid Them

Several issues can cause system state backup failures on a domain controller:

Insufficient disk space: System state can be several GB; ensure the target has at least 1.5 times the size of the system state.
Running without admin rights: wbadmin requires elevation; run PowerShell as Administrator.
Shadow copy service disabled: The Volume Shadow Copy (VSS) service must be running; check with Get-Service VSS.
Backup to the same disk as the system: This is not allowed; choose a different volume.
Using a non-NTFS destination: wbadmin requires NTFS for the backup target.

If a backup fails, check the event log under Microsoft\Windows\Backup and the wbadmin output for specific error codes.

Comparing wbadmin and PowerShell Cmdlets

Windows Server 2016 includes the WindowsServerBackup module with cmdlets like Start-WBSystemStateBackup, but they require loading the module and have similar limitations. The main difference is that wbadmin is a native executable that works in any PowerShell environment, while the cmdlets are more integrated but may not be installed by default. For scripting, wbadmin is often simpler because it returns text output that you can parse. However, the cmdlets provide structured objects and may be easier to use for error handling. In practice, many administrators use wbadmin in PowerShell scripts due to its reliability and simplicity.

Safety and Best Practices

Before running a system state backup, ensure you have a tested restore plan. The backup is only useful if you can restore it. Best practices include:

Schedule backups regularly (e.g., daily) using Task Scheduler to run your PowerShell script.
Store backups on a separate physical disk or network location.
Verify the backup by running wbadmin get versions after each backup.
Test a restore in a lab environment periodically.
Keep at least two backup copies (e.g., one local, one offsite).

Remember that a system state backup does not replace a full server backup; you should also back up other data volumes. For a domain controller, you may also consider backing up the system state before any major AD change.

Frequently Asked Questions

Can I use PowerShell to schedule a system state backup?

Yes, you can create a scheduled task that runs your PowerShell script. Use Register-ScheduledTask to run the script daily at a specified time. Ensure the task runs with highest privileges.

What is the difference between system state backup and bare metal backup?

A system state backup includes only the critical system files and AD database, while a bare metal backup includes the entire operating system, including system state, and allows restoring to new hardware. For domain controller recovery, system state is often sufficient if the OS is still functional.

How long does a system state backup take?

It depends on the size of the AD database and the speed of the target disk. Typically, it takes from a few minutes to half an hour. You can monitor progress with wbadmin get status.

Can I restore a system state backup to a different domain controller?

No, a system state backup is tied to the specific server and its Active Directory database. Restoring it to a different server would cause issues. For restoring to new hardware, use a bare metal backup or re-promote the server.

Do I need to stop Active Directory services before backing up?

No, wbadmin uses VSS to create a consistent snapshot while services are running. Stopping services is not required and would cause downtime.

What if I don’t have the Windows Server Backup feature installed?

You can install it via PowerShell: Install-WindowsFeature Windows-Server-Backup. After installation, the wbadmin command becomes available.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.