Restore Job Failure
In some cases, the restore job fails with the error message:
Aborting with error
Initiating a restore while the previous restore object still remains active will result in the failure of the new restore job.
This issue may occur owing to one of the following reasons:
- Multiple restore attempts to acquire a lock on the same namespace when a previous restore has been triggered. The job failure ensures only one restore is active at any given time and prevents resource name clashes.
- Job logs: Upon completion of a job, the restore object remains active for 90 seconds before being deleted along with the associated lock on the namespace. This allows the log scrapers to collect logs from the dbo’s ephemeral data-plane jobs.
Ensure that only one restore is active at any given time on a particular namespace, to avoid resource name clashes.