RPC Operations/sec Outstanding Exchange Server 2019

Bhupender Kumar 1 Reputation point
2021-02-09T15:14:37.547+00:00

We have added one new server into the existing production, OS 2019 Core, Exchange Server 2019. We have moved one of the databases DAG copy on this server and started to face performance issues and we check it via setting performance counter found that there is always a backlog RPC Operations/sec where on other servers its always on 0.

We moved back the DB to other servers and try to check the same with one DB which's having a single mailbox but again there is always RPC Operations/sec backlogs and which is increasing IS RPC latency so whoever client is connected to this CAS server started to face the slowness in accessing MAPI mailboxes.

We have checked all the Application and System Event logs but did not find anything related.

Server Hardware Configurations are below

HP ProLiant DL360p Gen8
Intel Xeon E5-2650L v2 @ 1.70GHz, 1701 Mhz, 10 Core(s), 20 Logical Processor(s)
Intel Xeon E5-2650L v2 @ 1.70GHz, 1696 Mhz, 10 Core(s), 20 Logical Processor(s)
Memory 128 GB
DISK Enterprise SSD (RAID 0)

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,457 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,123 questions
Exchange Server Development
Exchange Server Development
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Development: The process of researching, productizing, and refining new or existing technologies.
507 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,348 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yuki Sun-MSFT 40,856 Reputation points
    2021-02-10T09:07:07.65+00:00

    Hi @Bhupender Kumar ,

    From what I read, we usually check the status of both "RPC Operations/sec" and "RPC Requests" when troubleshooting slow RPC request processing issues. So you could check the RPC Requests performance counter as well and see how it goes.

    • If RPC Requests is steadily increasing while RPC Operations/sec remains fairly stable, this indicates that the server cannot handle the existing workload and it's suggested to verify hardware components or decrease the number of users on the server. (This doesn't seem to be applicable to your situation as your hardware configuration seems good enough and you have tried to leave a single mailbox on the server.)
    • If RPC Requests is steadily increasing but RPC Operations/sec steadily decreases, this indicates that the Exchange server is the source of the bottleneck. This kind of situation is generally caused by either a serious physical resource shortage (memory or disk) or a processing issue within the Information Store or an integrated component (antivirus, journaling, and so on).

    Reference: Troubleshooting Slow RPC Request Processing Issues.

    Furthermore, for current situation, if the users who report the performance issues are running Outlook in Online mode, it's recommended to switching to Cached mode instead which could potentially help improve the performance.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Bhupender Kumar 1 Reputation point
    2021-05-07T11:36:34.237+00:00

    Unfortunately, It's still same and even after getting Exchange server Installed on new server where MS support did nothing but waste a lot of time. Anyone is having any clue why this RPC Operations/sec backlogs from the RPC CLIENT ACCESS COUNTERS is not stable on just one server we are adding in existing Exchange 2019 Production. This is creating huge issues :(

    0 comments