Exchange issues
Check the Database availability groups cmdlet - use to find out if exchange server is the Primary or Secondary
- Get-DatabaseAvailabilityGroup
You can get all the details you need by using the following command:
- Get-DatabaseAvailabilityGroup | fl
- Get-DatabaseAvailabilityGroup -status
Sometimes the witness will fail, you can check the status of the witness by using the cluster resource cmdlet:
- ipmo failoverclusters
- Get-ClusterResource
This will tell you where the witness stores the file. If the DAG finds the resource unrelibale it might mark it as failed - you can restart this by using start-cluster resource:
- Get-ClusterResource | Start-ClusterResource
Issues with mail queue:
- use Exchange toolbox to open queue viewer
This will let you know if there are issues with incoming or outgoing emails.
Get info on server setup:
- Get-TransportConfig
- Get-TransportServer -Identity <servername> | fl
Show Database copy status between the exchange servers in a DAG:
- Get-MailboxDatabaseCopyStatus * | sort name | ft -autosize
Exchange Log Drive filling
Enable circular logging to flush transaction logs. This will mean you will not have the logs to perform a database restore
Go to Exchange Management Console and then go into Organization configuration, then Mailbox. On the database management tab there will be the databases. Click on the database and select properties, then in the maintenance tab click to enable circular logging.
Then Dismount and remount the database, this will clear the transaction logs.
Once logs have been cleared by mounting the database with circular logging enabled you should then dismount, disable circular logging and mount again. Then get the backups sorted.