• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 27 subscribers
  • Views 8317 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Understanding Schedule Logic & Strategy

Corrigun
over 7 years ago

Hi All,

A two parter-

1) Is there a good KB on understanding the scheduling logic? I read the "understanding schedules" but it didn't help past the obvious.

For example if you add a new machine using the wizard and set it to backup once a day at 5:00 PM the core creates a schedule with a start time of 5:00 PM and end time of 6:00 PM and a duration of 1:00 hr. However if you manually set a schedule to do this it takes a backup at 5:00 and another at 6:00. If you set it so start at 5:00 and end at 5:01 with a duration of 1:00 hr you get one backup. I won't even tell you how long I fought with a noon and midnight backup. I never did get it to work and used 1 and 1 is how.

2) What is the general consensus on scheduling many machines to backup and not become a mess of machines in queue?

I just added one server at a time on a once a day schedule, took a base image and then accelerated all the schedules once the backup sizes were under control. I'm not sure what will happen when it decides to re-seed.

Thanks,

Parents
  • 0 over 7 years ago
    Hi Tim,

    I still can't read the KB's as I'm having some license renewal issues and can't register. I have our renewed AA license files but RR seems to want something else. I have already contacted our rep and I'm sure he will straighten me out.

    No real concern with letting the queue stack up I just though I may be missing something. I am part of a large LAN/WAN that has other large backups running around the clock so we try to all get along and stay on our schedules.

    I will say I did try the 24hr 12-12 thing and was getting odd results with scheduled snapshots. Like skipping whole days. Maybe I just didn't let it run out long enough for it to auto correct but since I did it the way I described it's been dead on every checkpoint. And yes after the base image the incrementals have been short and sweet so it's working well even with exporting standby VM's.

    I will tag this solved.
Reply
  • 0 over 7 years ago
    Hi Tim,

    I still can't read the KB's as I'm having some license renewal issues and can't register. I have our renewed AA license files but RR seems to want something else. I have already contacted our rep and I'm sure he will straighten me out.

    No real concern with letting the queue stack up I just though I may be missing something. I am part of a large LAN/WAN that has other large backups running around the clock so we try to all get along and stay on our schedules.

    I will say I did try the 24hr 12-12 thing and was getting odd results with scheduled snapshots. Like skipping whole days. Maybe I just didn't let it run out long enough for it to auto correct but since I did it the way I described it's been dead on every checkpoint. And yes after the base image the incrementals have been short and sweet so it's working well even with exporting standby VM's.

    I will tag this solved.
Children
No Data