CMDB Data archiving

ayman_h · ‎10-18-2024

Hi all,

We are thinking of setting up archiving rules for our CMDB tables using the CMDB data manager to archive CIs if they haven't been discovered for 30 days.

Can someone confirm if an archived CI comes back to life (discovered again), will the existing CI record move from the archived table to the cmdb_ci table based on IRE rules or does this lead to a new record being created?

Regards,

Ayman

michaelward · ‎10-18-2024

Hi Ayman. My experience is that when the CMDB manager archive policy runs, a task is created to the fulfill such that the task is pending, the general 'Archive' scheduled job runs, the CI is moved to the respective archive table, then you can actually expect to have a new CI record created via discovery or a data source.

A way to test this, which I have, is to pick a CI class, preferably a simple CI class like 'computer' which may not have relationship requirements, and then follow these steps:

1. Create a CI manually either via a form or using the SNC.IdentificationEngineScriptableApi.createOrUpdateCI() API. i like to use the API because it affords me the ability to carry around a JSON payload. If needed, use the Identification Simulation tool to generate a payload.

2. Set the record's install status, lifecycle stage and status to 'Retired'.

3. Run the 'CMDB Data Manager Archive/Delete Policy Processor' scheduled job. This will generate a policy task, which you can then manually approve through the CMDB Data Manager.

4. Run the 'Archive' scheduled job. You may have to look at 'Todays scheduled jobs' to find it. This will archive your CI.

5. Use the Identification Simulation tool to test the creation of the CI, using the same payload. You will notice the output will indicate an INSERT vs. and UPDATE. This is the clue you will indeed have a new CI created.

6. Go back to step 1, and use the SNC.IdentificationEngineScriptableApi.createOrUpdateCI() API, passing in the payload which matches the CI. If using something like computer, a serial number will do, but I use a name and serial number.

7. You will notice the CI is indeed created with a different sys_id of course. You will also notice the archive table continues to hold the archived CI, provided the retention period has not passed before the CI is deleted.

I hope this helps.

View solution in original post

balajip64 · ‎01-17-2025

Policy task is pending since two days. How can we cancel them and retrigger those tasks?

bharris · ‎08-07-2025

The archive policy task is pending for us too. When I click into it the "review" button is grayed out. Any idea why that is happening?