Solved

Automatic deletion of retired client as per defined days

  • 17 February 2022
  • 10 replies
  • 904 views

Badge +8

Hi All,

 

I s there any automation that can be done to delete retired clients after say 28 days.

icon

Best answer by Greg Smolen 22 February 2022, 18:22

View original

If you have a question or comment, please create a topic

10 replies

Userlevel 2
Badge +3

@Rahul18081 You can run the “Audit Trail Report” -

 

Audit Trail report -

https://documentation.commvault.com/11.24/expert/38017_viewing_audit_trail_report_on_web_console.html

 

On the report, you can search for instances of “Retire Client”. You will see an output similar to the following screenshot:

 

 

 

Userlevel 7
Badge +23

@Rahul18081 , I believe you can get that data from these REST API calls but I’m not sure what no license would look like:

GET

Client Properties

http://WebConsoleHostName/webconsole/api/Client/{{clientId}}

https://api.commvault.com/#bdeffba6-a436-04ff-b018-0b64864d48c9

also check here:

https://documentation.commvault.com/v11/essential/45898_rest_api_get_client_properties.html

I’ll have someone confirm.

Badge +8

@Mike Struening  Thanks for the update. Request you to please update if there is any report they can fetch the list of retired clients.

Userlevel 7
Badge +23

We do have some docs on learning to create a Workflow, which might help you get started, though a Workflow like this would be quite complex (you’d need to make sure it is absolutely airtight and doesn’t delete the wrong thing, etc.).

Unfortunately, it’s not something simple enough that we could plan it out here and get it created.  You’ll need to define a mechanism to get the list, then delete based on that output, as well as have some checks along the way.

Give this tutorial a shot:

https://documentation.commvault.com/11.25/expert/49530_creating_sample_workflow.html

See how comfortable you are with the various pieces.  If you feel confident, you should be able to piece together the parts to accomplish this task; however, I would strongly advise contacting your Account Rep to look into Personalization Services.

Conversely, I can look into creating a CMR to get this function added, though there’s no guarantee it will be created nor any ETA.

Let me know what works best for you!

Badge +8

@Mike Struening   Yes, we have Client Computer groups and storage polices differentiating the clients for multiple projects.

i am not much expert in Work flow creation can you help me to create one.

Userlevel 7
Badge +23

In that case, you’re better of creating a Workflow to check the client list, pull the deconfigured list, and delete them.

I have a question though….if you have other projects that the aging setting would affect, how would you ensure this Workflow doesn’t delete those clients?  I’m assuming you have a Client group assigned to help filter things out?

Badge +8

@Mike Struening  Thanks for the update but there is a catch that there other projects whose backups are also been managed by same Commserve and setting this configuration will delete there data of de-configure clients after 28 days.

 

Please suggest 

Userlevel 7
Badge +23

Makes perfect sense, thank you!

What about using this option?

https://documentation.commvault.com/11.25/expert/11019_media_management_configuration_data_aging.html

This way, you can automate the backup deletion and solve your problem far more easily!

Days to keep jobs of de-configured clients

Definition: Specifies the number of days to retain the jobs of deconfigured clients.

Note:

  • Data Aging will honor the highest of storage policy copy days retention or the number of days specified in this parameter.

  • If you want to use only days retention and ignore the cycle retention, set Ignore Cycles Retention on De-Configured Clients parameters as 1.

  • Spool copy ignores this parameter and continues to honor the spool retention (zero days and zero cycle).

    Default Value: 0

    Range: -1  to 11000 days. (-1 is for infinite retention)

Badge +8

@Mike Struening :- We are using Commvault a Private Backup as a services were our Commvault admin team charges as per client backup consuming the storage. If the client is decommissioned and we have not deleted it from the Commvault then its backup will still be available and we will be charged. We can’t delete the client when its decomm from Wintel end as we need to keep it for 28 days as per our retention.

After 28 days we then can delete it from Commcell console. But as it requires manual intervention and if we forget to delete the retired client the Commvault admin team will charge us for the client that was decomm.

Hope you are able to understood my issue. 

Userlevel 7
Badge +23

@Rahul18081 , I’m not aware of anything built in.  You can likely create a Workflow to do this.

If I may ask, what is your end goal here?  There might be a better way to get you to your desired outcome!