KB ID: 102170
Cause:
Error 102170 occurs when a backup job is triggered manually or automatically while the backup server is still processing metadata updates from a previous backup operation.
Even though the earlier backup job may appear completed (either successfully or failed), the backup server continues updating internal database records such as:
Backup schedule information
DB Metadata Updates
Catalogue/index information
During this metadata update process, the backup server temporarily prevents another backup operation from starting for the same backup schedule or backup set to avoid metadata conflicts and maintain database consistency.
This issue can occur in the following scenarios:
A backup job completes successfully, but metadata updates are still in progress when another scheduled or manual backup starts.
A backup job fails, and the system initiates automatic retry attempts. During the retry interval, metadata/database updates may still be in progress, causing the next retry or another backup trigger to report Error 102170.
Backup schedules are configured too closely.
Database update operations are delayed due to high system load or database performance issues.
Solution:
This is generally a temporary condition and usually resolves automatically once the metadata update process completes.
To resolve or avoid this issue, follow these recommendations:
1. Wait for Automatic Retry
The backup server automatically retries the backup operation after the metadata update process completes.
No manual intervention is required in most cases.
2. Avoid Triggering Immediate Manual Backups
Do not manually trigger another backup immediately after:
A successful backup completion
A failed backup attempt
An ongoing retry operation
Allow sufficient time for backend metadata processing to complete.
3. Review Backup Schedule Configuration
Ensure that backup schedules are not configured too closely together.
If multiple schedules target the same backup, configure adequate time gaps for jobs.
4. Server Performance
Long metadata update durations may indicate:
Resource constraints on the backup server
Slow disk I/O operations where the DB data is being written
Additional Notes:
The previous backup job may appear completed while backend metadata processing is still active.
The retry protection mechanism helps maintain backup consistency and prevents concurrent metadata update conflicts.
If the issue persists for an extended duration or repeatedly occurs, contact support with the necessary logs for further analysis.