Monitor Exchange Server DAG and Database Health with PowerShell
Check DAG replication, verify backups, manage database copies, drain servers for patching, and report database size with a repeatable on-prem Exchange workflow.
Plenty of organizations still run on-premises Exchange — full deployments or hybrid mailbox servers that have to stay healthy. A Database Availability Group (DAG) is only protective if replication is healthy, copies are seeded, and backups are actually succeeding.
The problem is that DAG health, database state, and patch windows are usually checked manually and inconsistently. A failed copy or a stalled backup can go unnoticed until you need it most.
A repeatable PowerShell workflow turns those checks into a routine, and gives you a safe pattern for draining a server before patching. PSForge helps you build it from ready-made Exchange Server tasks.
The risk of manual DAG operations
DAG maintenance is high-stakes. Patching a server without putting it into maintenance mode can trigger an unplanned failover or leave databases mounted on the wrong node.
Likewise, a database copy that has quietly fallen behind — or a backup that has not completed in days — undermines the entire redundancy story. These conditions are easy to miss without a consistent check.
What a healthy maintenance routine looks like
A good routine regularly checks DAG replication health, verifies that database backups are current, and reports on mailbox database sizes so you can plan capacity.
When it is time to patch, the routine drains the server cleanly with maintenance mode, then reseeds or re-adds copies as needed and confirms everything is healthy before moving on.
Always drain before you patch Put the server into maintenance mode and confirm databases have moved before applying updates. Reverse the process and re-check replication health afterward.
How PSForge helps
PSForge gives you the Exchange Server building blocks — DAG health checks, copy management, backup verification, and maintenance mode — so you can assemble a safe, repeatable routine without writing every cmdlet from memory.
Generate the PowerShell, schedule the read-only checks, and keep the maintenance steps on hand for your next patch window.
- Early warning on unhealthy database copies
- Confidence that backups are current
- Safe, repeatable patch-window procedure
- Capacity insight from database size reporting
Example health-check workflow
- Check DAG replication health across all copies
- Check database backup status for currency
- Generate a mailbox database size report
- Flag any unhealthy or lagging copies
Example patch-window workflow
- Put the server into maintenance mode
- Confirm databases have failed over cleanly
- Apply updates and reboot
- Reseed or re-add any database copies as needed
- Re-check DAG replication health before bringing the node back
Final thoughts
DAG and database health checks are repetitive by nature, which makes them ideal candidates for a standardized workflow.
Build it once in PSForge and run the same trusted routine across every Exchange server you manage.