If required, you can disable replication to and from individual machines. For example, you may want to temporarily stop the CMS sending policy change notifications to all CA DataMinder machines. To disable replication, you can either suspend a machine or server, or you can set the replication period to zero.
When a CA DataMinder machine is manually suspended, it can neither send or receive replicated data. For client machines, this means they can neither replicate captured data to their parent server or receive policy changes from the CMS.
Note: If a machine is suspended automatically (for example, because of a critical shortage of free disk space), under certain circumstances events captured locally before the suspension are still replicated up to the parent server.
You need to edit the policy for the machine that you want to stop replicating data. In the Replication folder of the machine policy, set the Captured Data Notification Period and Infrastructure Notification Period settings to zero in order to separately disable the outward replication of captured data and infrastructure changes. Note that the machine will still be able to receive replicated data.
This approach is also the quickest way to turn off all replication across the CA DataMinder enterprise. First, set the notification periods to zero for the common gateway policy and the common client policy. Then do the same for the CMS machine policy.
Note: Be aware that this approach will generate extra network traffic as the policy changes need to be transmitted around the enterprise.
|
Copyright © 2014 CA.
All rights reserved.
|
|