Deconfigure and Reconfigure Components FAQ

Updated

I have deconfigured clients from older Commvault releases, can I reconfigure them?

Unlicensed clients from Commvault 9 or higher can be reconfigured.

During a CommServe upgrade, are deconfigured clients also upgraded?

If the CommServe software is upgraded to a new software release, any deconfigured clients from up to two prior releases will be automatically upgraded to the same software release. Thus, if a deconfigured client must be reinstalled, it will need to be reinstalled using the installation package for the same software release as the CommServe.

In cases where the deconfigured client is three or more releases older than the current release, the DBUpgrade utility can be used to upgrade the deconfigured client to the current software release.

Can I release a license for a component if I have the Administrative Management permission?

The users performing the "release a license" operation must have the Administrative Management permission for a CommCell entity at a higher level than the entity they want to deconfigure. For example, if you are releasing the license for a client, you must have the Administrative Management permission at the CommCell level.

I cannot remove the client from the CommServe Database, what can I do?

If a client crashes, and if you cannot remove the client from the CommServe database, you can use the release a license operation to remove the client. However, this does not uninstall the client.

What happens with the Data Retention policy when a component is deconfigured?

Commonly, the retention days must be exceeded for data to be aged when:

  • a user changes the storage policy association of a subclient

  • a client, agent or subclient are deleted, or a client or an agent is deleted

In these cases, retention cycles are set to zero (0). However, when you release the license for a client or an agent, the associated data will be aged according to the associated storage policy copy’s defined retention time and cycle rules. In this case, retention cycles are honored. If necessary, to ignore the defined retention cycle rules, you can enable the Ignore Cycles Retention on De-Configured Clients option from the Media Management Configuration (Service Configuration) dialog box in the Control Panel.

Can I configure a Remote Cache for a deconfigured or deleted client?

Yes, but all other clients associated with the remote cache will automatically receive their updates from the CommServe cache.

Can I review the list of components that I deconfigured?

Yes. Releasing license operations are recorded in the Audit Trail. See Audit Trail for more information.

To view a the list of deconfigured components, you can also connect to the CommServe database and run the query below:

select Distinct C.id as clientId, C.name as clientName, I.Id as instanceId, I.name as instanceName from APP_InstanceName I inner join APP_Application A on I.id = A.instance inner join APP_Client C on C.id = A.clientId where I.status=2
    

Can I restore a secondary copy if I retire a client that has aged primary copy?

Yes. For a client that has a secondary copy that is valid for X years and a primary copy that is aged, the retire operation retains the client and moves it to the deconfigured state for restore purposes.