Cmdlets
Get-MailboxDatabaseCopyStatus
-id <dbname> -server <servername>
Test-ReplicationHealth
-server <servername>
Suspend-MailboxDatabaseCopy
-Identity <DB\MBX>
Resume-MailboxDatabaseCopy
-Identity <DB\MBX> -ReplicationOnly (After the copy is resumed, it
remains administratively blocked for activation.)
Update-MailboxDatabaseCopy
-Identity <DB\MBX> -SourceServer <MBX2> -DeleteExistFile: $True
-CatalogOnly -DatabaseOnly
.\CheckDatabaseRedundancy.ps1
-MailboxDatabaseName <DB>
.\StartDagServerMaintenance.ps1
-serverName <MBX>
.\StopDagServerMaintenance.ps1
-serverName <MBX>
Events
Event
Viewer -> Applications and Services Logs
-> Microsoft -> Exchange -> HighAvailability
HighAvailability
that contains events related to the startup and shutdown of the Microsoft
Exchange Replication service and all the components that run within it, and
events such as a database mount, log truncation or events related to the DAG's
underlying cluster;
-> Microsoft -> Exchange -> MailboxDatabaseFailureItems
MailboxDatabaseFailureItems
is used to log events associated with any failures that affect a replicated
mailbox database;
-> Microsoft -> Exchange -> Troubleshooters
Troubleshooters
is used by some Exchange troubleshooting scripts such as the Content Index
Troubleshooter (Troubleshoot-CI.ps1) to log warnings and failures.
-> Microsoft-Exchange-Troubleshooters/Operational
-> MSExchange Management
If a
database is in a “bad” state for over 20 minutes (in duration, not consecutive)
in the hour-long run of the script, an EventID 4113 is generated and logged
into the local server’s Application log. If the database is “ok” for 10
consecutive minutes, an EventID 4114 is logged.
