OOB CMDB Data Manager Policies + archival question

[MrSmitty]

During testing with the Data Manager, I noticed there are 3 OOB policies already configured and activated:

Dependent CI Archival

Dependent CI Deletion

Dependent CI - Retire

Both the Deletion and Retire policies are generating tasks for what appears to be all relational type CIs - IP addresses, Network Adapters, Disks, and File Systems.  

For Retire, it seems self explanatory to a degree since the parent CI might be retired, a cascade action is necessary to retire the child/relational CIs.  For Deletion, it specifies that it's intended to delete dependent CIs which are orphaned.  It's confusing because these policies are essentially empty - no filter conditions are set and there is no subflow selected.  A couple of questions...

1.  Does anybody have any experience with these OOB policies, whether good or bad?  The intentions make sense but the logic does not, since the policies appear to be unconfigured.

2.  For archival policies, I understand that the data is moved out of primary tables but is still there.  Is there any kind of visible flag, or update that occurs during archival that can be documented?  I'd like to understand more about how the archival process works.  Edit:  Running a test, I can now see that archived records are moved to "ar_cmdb_ci_" tablesa and the Life Cycle data is set to empty.  The record is locked down and related records do not seem to be visible any longer.  There are related links to restore the record, and restore the record and related records.  Interstingly enough, restoring appears to keep BOTH records.  

[Bala Sruthi Mad]

Hi, Were you able to figure out the answers. We have the same questions

[MrSmitty]

No, and unfortunately, we now have CMDB Tasks being generated by the Deletion policy citing "orphan CIs" but they are not actually orphans.  I think we will have to adjust the relationship rules in the CI Class Manager to fix this.  

[james wells]

Those (3) policies only apply to the downstream child CIs of the Retired CI from your created Retire policy. You don't ever have to touch these (3) OTB policies. They activate and run automatically after you change/enable the system property for Dependent CI Management. These DM policies are good if you initially take the time to review all the data getting retired, and then getting archived. Definitely set 'Approval Needed' which will help the review, and start small. Wait to enable Dependent CI Management until after your created Retire/Archive policies are running as expected for like 6 months.