Backup set synchronisation fails or never starts because autonomic healing holds the same process priority

Backup set synchronisation fails or never starts because autonomic healing holds the same process priority

Machine-distilled from a resolved support ticket on 2026-09-28. Source ref: 5ba8f1c15c88. Verify before relying on it.

Applies to: DS-Client and DS-System (Asigra), any platform; version not specified in the ticket

Symptom: A backup set is reported as out of sync. Running a normal synchronisation, and also a DS-System based synchronisation, produces errors or never starts or completes. The event and activity logs show the sync failing each time.

Cause: A long-running autonomic healing process was active for the DS-Client. A process priority rule configured for that DS-Client gave synchronisation the same priority as autonomic healing, so the sync could not start or complete while healing was running.

Resolution: 1. Check the DS-System for any long-running autonomic healing (or other maintenance) process against the affected DS-Client. 2. Review the process priority rules for that DS-Client and check how synchronisation is ranked against autonomic healing. 3. Update the rule so the synchronisation is no longer at the same priority as autonomic healing. Alternatively, if appropriate, stop the long-running healing process or wait for it to finish. 4. Re-run the backup set synchronisation and confirm it completes successfully in the activity log.