windows server 2022 issue

Hello Vijaykumar Valadi,

When a Windows Server 2022 system state backup takes unusually long, the root cause is almost always tied to the volume of data being processed by the Windows Server Backup (wbadmin) engine and the way it interacts with the VSS (Volume Shadow Copy Service). A system state backup includes Active Directory database files (NTDS.dit), SYSVOL, registry hives, boot files, COM+ class registration database, and in some cases cluster configuration. If the server is a domain controller or has large registry hives, the backup can be significantly slower than expected.

The first thing to check is whether VSS writers are healthy. Run vssadmin list writers and confirm that all writers show a stable state with no errors. If any writer is in a failed state, the backup will hang or slow down while retrying. Also verify that the Windows Server Backup service is not competing with other backup agents (for example, third‑party backup software that also uses VSS).

Another common bottleneck is disk I/O. System state backups create shadow copies and then stream them to the backup target. If the backup destination is on a slow disk, network share, or deduplication volume, performance will degrade. You can test by redirecting the backup to a local SSD volume using:

wbadmin start systemstatebackup -backupTarget:D:

and compare the runtime.

If the server is a domain controller, the size of the NTDS database directly impacts backup duration. You can check its size under C:\Windows\NTDS\ntds.dit. Large AD databases with millions of objects will naturally extend backup time. In such cases, Microsoft recommends considering incremental system state backups or using Windows Server Backup with deduplication‑aware storage to reduce runtime.

Finally, review the event logs under Applications and Services Logs > Microsoft > Windows > Backup and VSS. These logs will show whether the delay is caused by retries, shadow copy creation, or data transfer. If you see repeated warnings about “VSS taking longer than expected,” it indicates a storage bottleneck rather than a software fault.

In short, the slowness is not unusual in environments with large AD databases or slow backup targets. The best practice is to ensure VSS writers are healthy, test backup performance to a fast local disk, and monitor event logs for bottlenecks. If the performance is still unacceptable, you may need to evaluate enterprise backup solutions that handle system state more efficiently than the built‑in Windows Server Backup.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.