Administration Guide › Machine Administration › Suspended Machines › Overview

Overview

Suspended machines overview

When a CMS, gateway or client machine is suspended, all replication and notification activity ceases. That is, the machine is unable to receive data such as policy updates or newly captured data. Suspended gateways and client machines also stop sending notifications of newly captured data to their parent server.

Automatic suspensions

CA DataMinder machines are suspended automatically if:

• Free disk space falls below the Error Level. This level is defined in the Infrastructure > Data Management folder of the machine policy.
• Database problems arise. For example, CA DataMinder suspends a machine if there is a communication failure with the local database, or if the local database becomes full (that is, it fills its allocated space quota).
• A disk failure occurs. If a parent server is unable to replicate data because of a disk failure on a child machine, CA DataMinder suspends the child machine.
• The replication holding cache becomes full. Events that fail to replicate successfully are stored in a holding cache. If the cache's maximum event limit is exceeded, CA DataMinder suspends the child machine. For details, see the Platform Deployment Guide; search for 'holding cache'.

Manual suspensions

You can also manually suspend a machine. You may want to do this to carry out maintenance. For example, a scheduled backup will complete faster on a suspended CMS.  This is because data transfers from gateways and client machines to a suspended CMS are discontinued until the CMS resumes data processing.

Note: To suspend or resume CA DataMinder machines, your user account must have the Edit Machine Hierarchy administrative privilege.

More information:

Disk Space Policy Settings