Applies to: Windows Server 2019, 2022 and 2025.
System-state backup is required for several AD DS recovery scenarios and must be protected together with a documented forest recovery plan.
Recovery procedures must be tested before an outage. Protect backup credentials and keep at least one recovery path separate from production. Visit managed Windows VPS hosting.
Prerequisites
- Use a domain controller with healthy replication.
- Install Windows Server Backup.
- Choose a separate target with enough space.
- Schedule and monitor the job.
Procedure
Step 1: Check directory health
Do not back up a controller with unresolved serious errors.
repadmin /replsummary
dcdiag /vStep 2: Start system-state backup
Replace E: with approved storage.
wbadmin start systemstatebackup -backuptarget:E: -quietStep 3: Monitor
Wait for completion.
wbadmin get statusStep 4: List versions
Confirm the copy is catalogued.
wbadmin get versionsStep 5: Store recovery documentation
Record DSRM handling and authoritative/non-authoritative procedures separately.
Verification
Review backup version and directory health after the job.
wbadmin get versions
repadmin /replsummaryRollback and recovery considerations
Backup creation does not change AD. If target selection was wrong, secure the misplaced copy and repeat to the approved destination.
Operational notes
A system-state backup from one controller does not eliminate the need for multiple healthy controllers and forest recovery planning.
Official references
For a hosted environment with setup and onboarding, explore our managed Windows VPS plans.