Schedule of Copies for Review

Hi,
Please check if I have correctly created a schedule that makes a full backup twice a day from Monday to Friday:

1-6/7-8,20-21

Hi,

While you have configured two windows when a backup can be run, it shows Mon-Sat (1-6) rather than Mon-Fri you mentioned…
07h00-08h00 and also 20h00-21h00

However, the setting related to full backup frequency, is based on a “number of days” count since the last one - meaning that [AFAIK] one per day is the lowest number (most frequent) you can have a full backup done…

Am interested in why you would want to have two full backups a day…would be simpler, not to mention more space efficient [should it have been possible to run fulls twice a day] to just run one full and then incremental for any additional backups…

For example, my webserver has a full backup done at silly o’clock in the morning, and then hourly incrementals for the rest of the day…

Hi,
I test different copy scenarios and I wanted to check if two full copies can be made on the same day. Is it possible to set in the program so that the copy is made exactly at 16:30, because I do not know if I think it should look like this: 1-7/16: 30-16: 30.

Hi,

The schedules are for the window that the backup/s can start (regardless of how long they take to complete) meaning that if you were to set that specific a “window” then you will most likely miss some…

For my setup, I have a full done at the weekend with incremental jobs during the week…have set window for that Full job to be based on the group the system is in, set staggered for a 3-hour window one day per week (for example “6/9-12” for one group, and “7/14-17” for another example group, though I have several groups) and the incrementals are set for the other days (“1-6/20-23” for example) and I then set the “between backup gap” interval to be less than the backup window…

Clarification of that, the full job is set for only one day a week, but I set the interval to be 3 days…means that the interval setting is then waiting for the “start window” for the job to begin, so it will always start at the beginning of the window…

Similarly, the incrementals only have a three hour start window, and have a 12-hour interval set…

Have got a couple of groups that don’t run incrementals (my VM hosts group) or are set for 1-hour intervals and have 20 hours in which they can start; the latter being a group that I want to capture more frequently, but the dataset is fairly small…

Again, make use of the groups, not only does it simplify config for when you have multiple servers with a similar role, but it makes replacement of a server a three-ish click affair to get the same setup…

Some of my groups only [currently] have a single system in them, but have got it set for wider environments…