Idea ID 1763366
This is an enhancement request to report skipped schedule backups .
The customer complains about that there is not any message/log for skipped schedule backups and the customer can not notice it .
Conflicted scheduled backup with the same backup specification will be ignored as described in the documents as follows .
Handle schedule conflicts
If a scheduled backup specification is running, and the same backup specification is triggered again while the current schedule is already running, the second backup specification is ignored, and is not queued to be run later.
For example, if 50 backup specifications are running, and are still in queued state; and in a 15 minute interval, the same backup specifications are triggered again, the new triggers are ignored.
However , the conflicted scheduled backup can be occurred very easily as follows .
- Full backup slowed down unexpectedly and it couldn't finish by the next incremental backup schedule
- The Conflicts Found option doesn't work when the schedule recurrence pattern is used
(conflicted scheduled backups can be configured)
So, customers should be able to know if scheduled backup was skipped .
- Skipped scheduled backup should be entered into "Missed job Executions"
- New notification event should be prepared for the skipped scheduled backup , or , for new records in Missed job Executions table
I have raised an ER QCCR2A83074 as well .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.