Recycle Bin for Deleted CIs in UCMDB

Idea ID 1677033

Recycle Bin for Deleted CIs in UCMDB

The aging reports are often hard to read, not monitored properly and aging may delete large chunks of data. Working with several UCMDBs I often need to see what has been deleted by enrichments or by mistake and eventually to undelete the deleted Cis. I would love to have the option to see what has been deleted in more detail that the Audit Report available in Custom Reports section, as well as eventually to undelete the CI and relationships in question.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

12 Comments
Acclaimed Contributor.
Acclaimed Contributor.

Would this data be useful form Solr/Recon Analyzer?

Acclaimed Contributor.
Acclaimed Contributor.

It would be interesting implementation, but isn't Solr retaining only the indexed attributes and the ranked CI types defined? Would that be enough to restore the CIs?

Another option, which we use in ServiceNow implementation, is to have a status = active/inactive attribute. When the status changes to inactive, the CI disappears. Of course in this case it should be done on an internal level.

Petko

Honored Contributor.
Honored Contributor.

Definitively very helpfull

Outstanding Contributor.
Outstanding Contributor.

We create similar utility by ourself. It check history and can repair deleted CIs and relations. If such function would be in OOB it would be good.

Micro Focus Contributor
Micro Focus Contributor
Status changed to: Waiting for Votes

Thanks for submitting. I agree on the usefulne of a easy to use recycle bin. Let's see how other customer are voting on this.

Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes

Honored Contributor.. Honored Contributor..
Honored Contributor..

I would love to this feature becoming available.   Also, not just for those CI's that have been deleted by Aging mechanism, but by users and other processes.

Outstanding Contributor.
Outstanding Contributor.

Just a note that this request is over 1.5 years old and is one of the most highly voted submissions ever.  Can we commit to putting this feature into development? 

Micro Focus Expert
Micro Focus Expert

We agree this would be a very useful feature.  However, the timing is tough because we would want to implement this as part of the CMS UI improvements and not in the Admin UI (as that is wasted effort for us).  Our focus on the CMS UI is still in getting the core Admin UI capabilities added to the product, such as adding the ability for folding and grouping of reports, a useful textual-based reporting UI, native CMS UI capabilities for properties, topology and impact widgets, and a useful "get related" capability.  

When we have those capabilities in the CMS UI, the recycle bin becomes high on our priority list.

When you think of a recycle bin, what use cases come to mind?  Our first thought was only for the use case of manual deletion of a CI, as a CI that was aged out should NOT be allowed to be restored.

Additionally, when you architect a recycle bin solution within the context of UCMDB, how far do you take it?  If you accidentally delete a node, a LOT of other data is deleted as well.  Do you allow for recovery of ALL the related CIs and relationships?  That will consume a lot of memory in situations where a CI (or multiple) are deleted.  Anyways, these are the thoughts we've already kicked around on this concept as we have considered it for implementation.

Super Contributor.
Super Contributor.

Last year we had a case where a uCMDB user inadvertently deleted 16 Nodes because he thought that he had selected 16 relationships to those nodes but had also selected the nodes themselves. Each node had about 2000 objects connected to it with Composition relationships (InstalledSoftware, Running softwares, Node elements, etc.). So a single delete operation had effectively deleted about 32,000 objects and as many relationships. It took us about 10 days to restore everything because we had to wait for 2-3 discovery cycles to run. Then, restoring the manual relationships that were created between Application CIs and the nodes/running softwares was a pain because all re-discovered objects had new Global IDs.

So, yes, recycle bin would only apply to manual deletion as aging, with the concept of "candidate for deletion", already gives a warning of a pending automatic deletion.

With our experience, I think that the recycle bin would have to include the deleted CI, it's immediate relationships, all CIs that would be deleted in the "cascade" effect of the Composition relationships and the immediate relationships of those cascaded CIs. I agree, that can mean a lot of CIs!

Sometimes, implementing a feature like that is as simple as adding a "deletion date" special attribute to the CIs and relationships. By default, only items with a NULL deletion date would be displayed. Someone with a special privilege would then be able to enable "Show deleted CIs" in his session to make them visible and be able to undelete them. Just like with aging, deleted CIs would be physically removed from the database after a specified number of days. Of course, even if the CIs in the recycle bin are technically present, they would not be processed to be merged with non-deleted CIs.

Currently, in order to compensate for a lack of recycle bin, we make a daily backup of all the manual relationships in order to be able to restore them in case an unwanted deletion occurs. It is not a perfect recovery solution, but it saved our a** a couple times in the past.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.