• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 27 subscribers
  • Views 8319 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

    Here is the info from that KB: 

    Backup window – The backup windows dictates the period of time in which a backup for that agent may be initiated. For example, if the backup window is set from 12 AM – 1 AM, then backups may be initiated for that agent starting at 12 AM but not after 1 AM. Hence there is a 1 hour period of the day where backups may run. 

    Snapshot interval – The snapshot interval dictates the interval at which snapshots will be taken within the backup window. For example, if the backup window is 1 hour long and the snapshot interval is set to 1 hour, then only 1 snapshot will be initiated during the backup window. If the backup window is 1 hour long and the interval is set to 15 minutes, then as many as 4 backups may be initiated during the backup window. 

    Click To See Full Image.

     
     
     
     

    Maximum Concurrent Transfers - The maximum concurrent transfers setting specifies how many backups may be running at the same time. By default the value is set to 3, which limits the number of simultaneous backups to 3. If the maximum number of backups allowed to run are already in process, the scheduler will wait until a backup slot becomes available before it will initiate the next backup. This means that it is possible for a backup not to be initiated because there is never an available slot during it's alloted backup window. 

     

    This process may cause issues for customers who are running only 1 backup per day and have a large number of agents. For example, if the backup window for 20 agents is set to 1 hour (12 AM - 1 AM) and the interval is set to 1 hour that means that only 1 snapshot will be taken for each agent that day.  However if the maximum concurrent transfers is set to 3 that means that only 3 backups will run at the same time. If the backups of the agents takes longer than 1 hour, there is a high likelihood that a number of agents will not backup because there is never a free backup slot during the backup window. 
     
    To avoid this issue, ensure that the backup window is set long enough that all backups can complete within that time frame and that the interval is still the same length or longer than the backup window (otherwise more than one backup will be taken). 
Reply
  • 0 over 7 years ago

    Here is the info from that KB: 

    Backup window – The backup windows dictates the period of time in which a backup for that agent may be initiated. For example, if the backup window is set from 12 AM – 1 AM, then backups may be initiated for that agent starting at 12 AM but not after 1 AM. Hence there is a 1 hour period of the day where backups may run. 

    Snapshot interval – The snapshot interval dictates the interval at which snapshots will be taken within the backup window. For example, if the backup window is 1 hour long and the snapshot interval is set to 1 hour, then only 1 snapshot will be initiated during the backup window. If the backup window is 1 hour long and the interval is set to 15 minutes, then as many as 4 backups may be initiated during the backup window. 

    Click To See Full Image.

     
     
     
     

    Maximum Concurrent Transfers - The maximum concurrent transfers setting specifies how many backups may be running at the same time. By default the value is set to 3, which limits the number of simultaneous backups to 3. If the maximum number of backups allowed to run are already in process, the scheduler will wait until a backup slot becomes available before it will initiate the next backup. This means that it is possible for a backup not to be initiated because there is never an available slot during it's alloted backup window. 

     

    This process may cause issues for customers who are running only 1 backup per day and have a large number of agents. For example, if the backup window for 20 agents is set to 1 hour (12 AM - 1 AM) and the interval is set to 1 hour that means that only 1 snapshot will be taken for each agent that day.  However if the maximum concurrent transfers is set to 3 that means that only 3 backups will run at the same time. If the backups of the agents takes longer than 1 hour, there is a high likelihood that a number of agents will not backup because there is never a free backup slot during the backup window. 
     
    To avoid this issue, ensure that the backup window is set long enough that all backups can complete within that time frame and that the interval is still the same length or longer than the backup window (otherwise more than one backup will be taken). 
Children
No Data