Archive Functionality in Servicenow

[GayathirriRadha]

Hi Friends,

Has anybody implemented Archive functionality for your customer. Please share your experience and let me know if there is any performance concern if the schedule run during peak hours. I understand by default there are 10 iterations happening per hour and each iteration archive 100 records.

My environment is 4 years old and I am wondering it will take time to complete the process to archive all the old records.

Regards

Gayathirri

[Chris M3]

We turned on Data Archiving in Feburary, about 3.5 years after our implementation went live, and with ~   1 million total records to archive from the various tables.   Our calculations suggested about a month to 'catch up', so instead we bumped up the properties for the first weekend, archiving 1000 records every iteration.   There was no mention from the people that use the system over the weekend of performance issues.

[sergiu_panaite]

Hello Gayathirri,

Before turning on archiving on production you should do some tests on a subproduction instance with data from a fresh clone of production.

With default settings the instance will try to archive 100 records x 10 iterations within one hour (the scheduled job
"Archive" runs every hour). It must finish within one hour all records it has to archive, otherwise a new run of scheduled job "Archive" will cause a second background archiver to run, which is not recommended. 1000 records are usually archived in a matter of a few minutes (most I've seen so far go up to 10 min), so increasing the number of records per batch is the first thing I would do. You should test going from 100 records per batch to 1000 (meaning 10000 records per hour).

The overall load of the instance can impact archiver to run slower or faster, so testing is the key here.

Regards,

Sergiu

[GayathirriRadha]

Thanks for the wonderful suggestion. We will take care of those items when we perform this in our instance.