I understand, now, how to manage the number of tries for a backup over a given period (global attributes in host properties of the master server). However when I am dealing with a failure and have resolved it I can't find a way to reset the policy so it will get back on the schedule. I am having to wait until the backup attempt interval is up (in our case that's 12 hours).
Here's my example... My master server global attributes are set to 2 tries per 12 hours (I think those are defaults but I certainly don't know). I have an archivelog backup of an oracle database that runs hourly.... and must or I will fairly quickly run out of space on the volume (lets assume I can't add any disk). Recently this backup failed... twice.... which is the maximum per 12 hours so the schedule will not pick back up even on a successful manual run. Since I really can't wait the 12 hours for it to pick back up on the schedule, I'd like to reset the schedule so that it will pick back up right now. However I can't find any sort of command that resets the tries or simply gives the policy a 'clean slate'.
So... what's the best thing to do here? I really don't want to change the global policy for my job that failed, but perhaps that's the best approach?