Search the Community

My main backup job "Nightly Backup" has four schedules: Schedule #1 runs Monday-Friday at night Schedule #2 runs Sunday at 1am once a week. Keep for 3 weeks Schedule #3 runs Sunday at 1am once a month. Keep for 4 months. Schedule #4 runs Sunday at 1am once a year. Keep for one year. I enable "Prioritize schedules" since by design the Sunday jobs all start at the same time, and I want the latter ones to take priority over the earlier ones. i.e. if #3 is triggered to run - don't run schedule #2. Likewise if #4 is triggered to run, don't run schedules #3 or #2. My repository is setup for deduplication. The data I'm backing up - the bulk of it rarely changes. This fact, combined with the deduplication repo, gives me the luxury of being able to set those additional schedules with really long retention times. This all works beautifully except for one thing. Every month I get a alarm telling me that "1 Issue requires your attention". See attachment. Yes Nakivo - I know about that! Yes, job schedule #2 should be skipped for job schedule #3. that's how it's designed, and it is working as designed. Same goes for Schedule 4 taking priority over #3 and #2. It's all fine. Nothing to be alarmed about. Alarms should not be generated for something working as designed. Can you please stop raising these bogus alarms? Thank you.

I see a little bit about job chaining in the manual but I don't see any documentation on how to set it up. Can anyone advise on this?