Cloud Data Manager

Managing agents

To manage the agents, use the top menu to navigate to the AGENTS tab. The top section of the AGENTS tab contains details regarding the health and status of the server as well. See Server status for more details.

Defining a new agent

image70.png

Enter the required input as shown in the example above:

Name

The agent name to be displayed in the management server

Hostname/IP

The IP or DNS of the target z/OS

Port

The port used by the agent, as set during the agent installation

Test the connection from the management server to the new agent:

image24.png

An error message is displayed if an error is detected when attempting to communicate with the agent:

image6.png

Viewing agent details and status

Viewing agent details and status

Using agent group for sysplex support and load balancing

An agent is associated with an agent group in the agent configuration file. By default, each agent is part of an agent group in the name of the Sysplex. When associating a policy with an agent group, the tasks are executed by the agents in the group in round-robin fashion. By default, the server sends 10 tasks per agent simultaneously.

image4.png

At the beginning of an activity, the run log identifies all the agents that are available for executing tasks. Upon completion of the task, the specific executing agent for every backup/archive operation is identified.

If an agent has more than 5 communications failures, the server stops sending it tasks during that activity. The number of allowed failures can be configured on the server.

The first phase of identifying the resources for processing is performed by a single agent.

Agent group load balancing can be used for sharing work, but also for limiting it to specific LPARs. It may be defined, for example, that all LPARs in the same Sysplex share the same resource complex, allowing them to recall and restore the same resources. However, the archive and backup policies are defined to work with an agent group containing only a subset of the LPARs.

Restore, recall and export behaviour when using an agent group policy

Recall / Restore from CLI

Recall and Restore can be performed by any agent sharing the same resource complex as the agent that performed the original backup, dump or archive. By default, the resource complex is shared by all agents in the same Sysplex, but note that only agents on LPARs that also share the same z/OS Unix System Services can be candidates for this action.

Automatic recall

Automatic recall is executed on the same LPAR that initiated the request. If there are several agents on the same LPAR, any of them may pick up the request.

Recall from the UI The server will attempt to use the original agent that executed the archive operation. If that specific agent is not available, the action will fail.

Restore from the UI The server will search for the first available agent from the agent group that was used for the archive. If no agents are available, the action will fail. If there are no agents connected to the agent group, the action will also fail.

Export from the UI The server will search for the first available agent from the agent group that was used for the archive. If no agents are available, the action will fail. If there are no agents connected to the agent group, the action will also fail.

Updating existing agent details

Edit_Agent.png
Edit_Agent_Modal.png

When done editing, click “Save” to update the agent settings.

Deleting an agent

Deleting an agent requires that it will not be associated with any policy.

image33.png

Confirm:

image69.png