Pausing and Resuming a Territory Gateway
You can temporarily halt the flow of documents from a territory gateway to a remote territory by pausing the territory gateway. When you pause a territory gateway, the gateway locks the forward queue that it maintains for the remote territory. This action prevents the remote territory from retrieving documents from this territory gateway.
No documents are lost when you pause a territory gateway. The forward queue on the territory gateway continues to accumulate documents for the remote territory, but these documents will not flow to the other territory until the territory gateway is resumed.
Be aware that pausing a territory gateway halts the flow of outbound documents (documents that originated from the territory on which the territory gateway resides and are being forwarded to subscribers in the remote territory). It does not prevent that territory gateway from receiving documents from the remote territory. To halt the flow of inbound documents, you must pause the territory gateway in the remote territory, too.
Note:
Administrators often pause a territory gateway when the territory that the territory gateway represents is undergoing service or significant configuration changes. For example, if you intend to make numerous changes to document types or permissions, you might pause the territory to ensure that all the changes are propagated to the other territory at one time.