It certainly sounds like something network related.
One things Commvault is very susceptible to is firewalls transparently dropping connections. This is because many Commvault processes make connections that remain idle until the state changes. For example, it could take a long time to complete copying a chunk - during this time a firewall may detect the connection as idle and close it, transparent to Commvault and even the Operating System - until it tries to update the CommServe or remote MA about the success of the chunk copy.
One way around this scenario is to implement a network (or firewall or network topology) configuration which then changes the way Commvault initiates communication. Instead of raw TCP connections, it tunnels all connectivity over a single TCP/IP connection. There is also a higher level of built-in resiliency and keep-alive that occur with this method.
Check out this video that explains a bit more and shows you how to implement a network topology:
https://documentation.commvault.com/2023e/expert/search.html#q=Overview%20of%20Commvault%20Network%20Configurations&t=All&sort=relevancy&f:commonsource=[Educational%20Videos]