When Exchange Server experiences too much load and doesn't have the resources to perform its services, a transport...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
server's back pressure mechanism engages to prevent server failure.
The Exchange back pressure feature throttles or halts mail flow to keep Exchange Server functioning. Exchange Server administrators must monitor the infrastructure to determine how much pressure servers are under and avoid error messages or a halt in mail delivery.
Admins can use PowerShell to retrieve diagnostic information from Exchange Server.
Get-ExchangeDiagnosticInfo -Server MBX1 -Process EdgeTransport -Component ResourceThrottling
The results (Figure 1) are presented in XML format instead of the standard PowerShell output, which prevents the use of the Select-Object cmdlet to view the individual values. But we can tell the Exchange Management Shell to display a specific piece of XML data.
To do this, administrators must to know that XML tags are hierarchical. The third line in Figure 1 has a tag named ID. To display the ID value -- in this example, 6340 -- refer to the other tags in the hierarchy. The top level tag is Diagnostics, the second level tag is ProcessInfo and the third level tag is ID. So we would reference Diagnostics.ProcessInfo.ID, rather than call ID directly.
The easiest way to do this is to assign the Get-ExchangeDiagnosticInfo command to an XML variable. This assignment works the same way as with any other PowerShell variable, except [xml] must be specified before the variable name to pull data from the variable.
To see this in action, determine the current working set size. The first step is to declare a variable with this command:
[xml]$BP = Get-ExchangeDiagnosticInfo -Server MBX1 -Process EdgeTransport -Component ResourceThrottling
Then retrieve the working set size by referencing the variable and the required tags. In this case, the command is:
In Figure 2, the working set is reported as 187.1 MB.
Figure 2 also shows a few empty returns and then the command $BP.WorkingSet, which offers no output. This shows why administrators must specify all XML tags in the hierarchy to display the requested data. If you expect to see results but do not get an output, check to see if you omitted or misspelled a tag.
Understanding Exchange back pressure information
Figures 1 and 2 show limited information because the commands were run on a mailbox server -- not an edge transport server -- to build familiarity with XML. Running commands on an edge server delivers more details.
Type the Get-ExchangeDiagnosticInfo command, but use the edger server name. This will yield a different output. Figure 3 shows truncated results from this command:
Get-ExchangeDiagnosticInfo -Server E2K16Edge -Process EdgeTransport -Component ResourceThrottling
To see the full set, append the Select-Object cmdlet, along with the -ExpandProperty parameter, followed by the word Result. The full command is:
Get-ExchangeDiagnosticInfo -Server <server name> -Process EdgeTransport -Component ResourceThrottling | Select-Object -ExpandProperty Result
Figure 4 shows a small portion of the output.
The XML data lists a number of different Exchange Server resources. For each resource, Exchange lists the pressure and the pressure transitions. It also lists the current and previous resource use. For example, Figure 5 shows resource meter data that's related to DatabaseUsedSpace and indicates that the resource is currently at low pressure and had been under low pressure before. The current pressure reading is 4.
Admins can use the Exchange Management Shell to monitor pressure and pressure changes on edge transport servers. Microsoft provides an explanation of various Exchange back pressure metrics online.
Use logs to detect server pressure, analysis
Virtualization considerations for Exchange 2016
Use PowerShell commands for faster Exchange mailbox management
Dig Deeper on Microsoft Exchange Server Scripts and Programming