ISE 2.x || Looking for best practices on daily Vs weekly Scheduled jobs/Backups

[musultan]

Hello Team,

I am looking for best practices on Scheduled jobs like Config Backup, OPS Backup, Endpoints Purging, Reports.

For backups, what are the pros and cons for the weekly vs daily? We see that OPS backup fails on different time due to some background DB operations and it aborts.

What should be the scheduled time for the scheduled reports Vs endpoints purging Vs Config Backup Vs OPS Backup?

Off-course, it should be off-peak time and see the related ENH bug: CSCvb73747 --> ENH: Scheduled configuration backup not to be permitted between 12 am and 4 am https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb73747

Try to answer inline, if possible.

[hslai]

ISE has certain activities, such as endpoint purging, have fixed schedules and are not configurable. Many of these could be resource intensive so other scheduled tasks need avoid done around these intervals.

In general, I would suggest to take daily backups on CFG and immediately before and/or after any major changes. As to OPS, it's best to use it to troubleshoot recent events but not to take backups if it fairly sizable. Instead, I would recommend to forward the ISE events via Syslog to other aggregators, such as Splunk.

[musultan]

Thanks for the reply.

I just want to clarify about the statement if i understand it correctly endpoint purging, have fixed schedules and are not configurable.

I believe we can configure it as per our requirement when to purge and select days and time.

See the below;

[hslai · Accepted solution]

Thanks a lot for the correction. A better example would be ISE daily DB cleanups and other maintenance jobs.