Deconfigure Clients with no Backup History

I think you’re going to have to use groups of rules - one rule wont rule them all. Ha Ha. 😅

I think you are on the right track with “days since last backup” - you’ll need to add rules to filter out pseudiclients (discovered VMs) or index client (I think there are rules for that) until you have a client list that matches your requirements.I don't see anything cookie cutter that will make this easier other than what you have already discovered.

If you are already manually disabling the schedule or activity on a client, why not retire it at that time using the retire option? that could save you the headache of automating around a manual function anyway.

@RobAbate 
 

If retiring client feature doesn’t meet your needs - Only way I can see you get something like this is via a custom workflow which you coordinate with your CV account manager. These usually incur costs for design / creation however. 

Thanks,

Chris

Damian - we do not want to use the retire functionality because we often get decommission requests followed by requests to put them back into production (happens surprisingly frequently around here in MSP environment).  Therefore this option to disable backup activity seems to be the best option for our environment, as it would allow us the flexibility to quickly put things back into production if needed, while retaining the schedules and all other settings.

I assumed that the built-in ClientDeconfigure workflow was going to accept a client group as input (because why would I need a workflow to deconfigure just one client when I can simply do that interactively) - but of course, it only accepts one client as input.  If the workflow accepted a group it would work great and I would have the functionality working the way I want it to.

The “retire” feature does not meet our needs and tries to do too much at once.  Like I said, I’ve already got the hard part done - and I’ve got the clients I need to deconfigure contained within a group with data aged off.  So at that point I can just deconfigure them - which would just be cleanup as the data would be aged off already - so no urgency to deconfigure at that point.

I was really looking for another MM Data Aging parameter to accomplish this - there’s one to automatically delete deconfigured clients with no protected data - so the only missing link is a process to deconfigure them -- I want it to be tiered where activity is disabled for 35 days, then data is aged off, then it gets deconfigured and stays for 30 days and then is finally deleted.

I realize that this is not the way most customers would do things - but this is the way we want it to work for our environment and needs.

The “RetireClients” report sounds like what i am looking for since my clients are not auto deleting like they should.  I do not see the report any longer.  Is it gone?

This should have the old clients auto clean up...

Update.

     Working with support the “Delete deconfigured clients that have no protection data’, does work.  In my case my clients are not going away since we still have aged backups on tapes.  The client will stick around until the tapes are overwritten.   The other option to get rid of the aged jobs on tape, is to set the “Prune the jobs on tape media when the retention criteria is met” in the control panel.