Troubleshoot Scheduled Backup Failures in ISE

Available Languages

Download Options

  • PDF     (19.8 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (79.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (64.3 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:August 31, 2026
Document ID:226309

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Issue

Cisco Identity Services Engine (ISE) stops generating scheduled backups. Automatic backups fail to generate or retain, which impacts the ability to create and store configuration backups needed for system recovery. Both scheduled automatic backups and manual GUI-initiated backups fail, creating a business impact related to backup reliability and system recovery preparedness.

Environment

  • Cisco Identity Services Engine (ISE) versions 3.3, 3.4, and 3.5 earlier than patch 3

  • Scheduled Config and/or Operational Backups configured

  • Telemetry Enabled

Resolution

1. Access the Cisco ISE CLI and execute the command app configure ise.

2. Select option 23 to generate a thread dump for diagnostic purposes.

3. Collect a support bundle from the primary admin node, ensuring logs cover the last 10 days.

4. Review the ise-psc.log over the 10-day period for entries with DefaultQuartzScheduler_Worker- followed by numbers 1 to 10.

note-icon

Note: One of these worker threads disappear daily until none remain, indicating scheduled jobs are no longer running.

5. Search catalina.out for the line containing com.cisco.cpm.infrastructure.telemetry.api.TelemetryJob.execute.

6. Identify Cisco bug ID CSCwr39748 if the telemetry job execution line is present.

7. Navigate to Administration > System > Settings > Network Service Diagnostics > Telemetry in the ISE GUI and disable the Telemetry feature.

8. Reload Primary Admin Node to clear the current threads stuck.

Cause

The root cause is Cisco bug ID CSCwr39748. This defect causes the DefaultQuartzScheduler_Worker threads to be blocked by the daily telemetry service. These threads are never released, and all 10 threads become consumed, preventing scheduled actions from running. The presence of the com.cisco.cpm.infrastructure.telemetry.api.TelemetryJob.execute line in the catalina.out log confirms the system is affected.

Related Content

Revision History

Revision Publish Date Comments
1.0
31-Aug-2026
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Ethan Glaser
    Technical Consulting Engineer

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products