If I have transaction logs on a separate drive does Exchange backpressure monitor that drive?

The following link discusses the 'message queue' database transaction logs but these seem to be different from the database transaction logs - https://technet.microsoft.com/en-us/library/bb201658(v=exchg.150).aspx

We recently had an issue that brought into question whether this drive is being monitored. Unfortunately we didn't have old enough event logs to go through for backpressure events.

If I have transaction logs on a separate drive does Exchange backpressure monitor that drive?

The following link discusses the 'message queue' database transaction logs but these seem to be different from the database transaction logs - https://technet.microsoft.com/en-us/library/bb201658(v=exchg.150).aspx

We recently had an issue that brought into question whether this drive is being monitored. Unfortunately we didn't have old enough event logs to go through for backpressure events.

in Exchange 2013 Managed Availability monitors disk space. 100GB is the threshold I believe. Any events would in the Man. Avail event logs

Thx Andy!

Is it 100GB or a particular % of drive space? What if my total log drive is only 80GB? Do you have a link to a whitepaper detailing this?

Edit - ...and as a followup, is this just monitoring? I'm concerned that Exchange DOES NOT take corrective action (like backpressure is supposed to) for the transaction log drive.

• Edited by Alceryes 12 hours 48 minutes ago

Thx Andy!

Is it 100GB or a particular % of drive space? What if my total log drive is only 80GB? Do you have a link to a whitepaper detailing this?

Edit - ...and as a followup, is this just monitoring? I'm concerned that Exchange DOES NOT take corrective action (like backpressure is supposed to) for the transaction log drive.

MA is a can of worms, but you can look at things like adjusting storage monitor thresholds:

http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx

If you are worried about running out of diskspace in the transaction log drive, look at loose truncation instead:

http://windowsitpro.com/exchange-server-2013/loose-truncation-exchange-server-2013-sp1