02-03-2017 08:37 AM
I have a policy (Standard) to backup some files (exported MySQL logs) hourly. The Full schedule runs at midnight (window 00:00-02:00) and DIFF (hourly) runs every hours from 0200-midnight.
I have noticed that if the DIFF backup fails and is resubmitted by our operations team manually, it does not run hourly for next several hours.Last time it took 10 hours to start running the hourly backups. Last time we had a few failures (58 or 25) was in December and I had noticed the same thing.
Can someone shed some light on this "hiccup" of the scheduler?
Master/Media are RHEL 6 x64 with NetBackup 7.7.3. Client is RHEL 5 x64.
Solved! Go to Solution.
02-03-2017 11:13 AM
02-03-2017 11:13 AM
02-03-2017 11:38 AM - edited 02-03-2017 11:39 AM
Thanks Marianne for the information.
Are you referring to the Global Attributes (highlighted in the attached)?
02-03-2017 11:42 AM
02-07-2017 07:36 AM
Thanks.
I'm trying to reproduce it in my test environment and if everything is OK, will make change in production and mark earlier post as solution.
02-09-2017 05:57 AM
Update: I recreated the setup and was able to reproduce the issue in testing environment. After changing the Global Attribute for attempting backup "1 tries every 1hours", the backup was not skipped.
Thanks for the pointer @Marianne.