Deconfiguring Agents - How To

Deconfigure a Client, MediaAgent, Agent, or Enabler

Administrative Management capability cannot be used to perform the deconfigure operation from the MediaAgent level.

Before you Begin:

For MediaAgent Deconfiguration, ensure that all the storage policies or copies associated with the configured libraries (or drive pools) in the MediaAgent are deleted or re-associated to another MediaAgent.

To deconfigure a client, MediaAgent, agent, or enabler:

In the CommCell Browser, right-click the name of the client, MediaAgent, agent, or enabler you want to deconfigure, click All Tasks (if displayed), and select Deconfigure.
A popup warning message appears.
Click OK to continue.
Another popup message then appears.
Click Yes to continue with the deconfiguration or No to abort.
If the deconfigure is unsuccessful, a number of popup messages appears. In some cases, the message requests that you take some corrective action. For example, the message might advise you to ensure that there are no jobs running on the agent. In such a case, click OK and take the appropriate action. Then repeat the deconfigure process.

If the deconfigure is successful, the tree element is dimmed and available for deletion.

To suspend use of a client computer temporarily:

Create a New Scratch Pool that does not contain any media, and name it No_Media. Note that a scratch pool with no media associations does not harm any existing configurations, nor does it misuse media.
Create a Storage Policy (standard), name it No_Backups, and point it to the No_Media scratch pool.
Disable Operations for the client that you are temporarily disabling.
Verify that the Queue Jobs if Activity Control is Disabled option is disabled. This will reduce the number of queued jobs in the Job Controller.
Re-point all the client's subclients to the No_Backups storage policy. When a user changes the storage policy association of a subclient, retention cycles are set to zero (0), therefore, only the retention days must be exceeded for data to be aged. In this case, the data in the storage policy to which the client's subclients were originally pointing to will age accordingly. Note that if the client computer's activity is re-enabled, you can point the subclients back to their original storage policy.
To resume client activity: Enable Operations for the client, and point the subclients back to their original storage policy.

NOTES

This feature does not require a user to uninstall client software; therefore, no licenses are released during this process.
Any scheduled jobs associated with the suspended client will cause job failures when initiated. This is normal behavior. Once client activity is re-enabled, these scheduled jobs will no longer cause job failures.

To hide deconfigured clients:

The deconfigured clients should now be hidden from view.