The support forum

Quiet times / Scheduled Hours

Aug 29, 2017

Starting with Release 78 it's possible to suppress scheduled and real-time backups in certain time/day periods - a feature referred to as "quiet times" or "quiet periods".


Quiet times (QT) are configured on per-backup basis. It's possible to have more than one QT specified for a backup job.

When a job enters a quiet period, the backup engine will not schedule any backup runs until the period is over. If a backup is running when a quiet period starts, it will continue running as usual, to completion.

A job in a quiet period can still be run manually at any time.

Each QT entry comprises the starting date/time and duration. It may also have a "repeat" attribute, which will do what it implies - repeat the QT as specified.

It is also possible to specify a day of the week as the QT's starting point. This is meant to support a very common case of mandatory weekly blackouts.

Aug 29, 2017

Configuring quiet periods

Configuring quiet periods for a job is done by manually adding period definition to the job's configuration file.

        For how to find and edit job's settings.ini see -

Each quiet period is described by its own "conf.quiet_time" line, e.g.

        conf.quiet_time    2017-08-29 12:34, 3 hours

This defines a 3 hour quiet period starting at specified date and time.

        conf.quiet_time    2017-08-29 12:34,  3 hours, 12 hours

Same, but the period is then repeated every 12 hours.

Note #1 - the "start" point can be set into the future. This can be useful for scheduling one-off quiet periods around one-off external events.

Note #2 - the "repeat" interval must not be shorter than the QT "duration," e.g. something like this is a configuration error and it will cause the job to be disabled on load:

        conf.quiet_time    2017-08-29 12:34, 10 hours, 2 hours

Aug 29, 2017

Weekly scheduling

Simplified notation can be used to schedule weekly quiet periods:

        conf.quiet_time    Monday 12:34, 10 hours

A day of the week followed by HH:MM, comma, followed by duration.

It's also possible to specify the repeat interval, but it must be a multiple of one week. E.g.

        conf.quiet_time    Monday 12:34, 10 hours, 3 weeks
        conf.quiet_time    Monday 12:34, 10 hours, 14 days

are both acceptable, but

        conf.quiet_time    Monday 12:34, 10 hours, 3 days

is not and it will yield a configuration error on job's load.

Dialp :

Sep 15, 2017

Thanks, Alex! I was really looking forward for this feature.

I've just configured my backups to skip the weekends, let's see how it works out!

kostas.michas :

Sep 29, 2017

Hi guys,

When will that be ready on the user interface please?


Alex Pankratov :

Sep 29, 2017

Most likely in a couple of major releases - in R80 or thereabouts, which is 2-4 months from now.

kostas.michas :

Oct 30, 2017

Ok thank you Alex

New topic

Made by Pipemetrics in Switzerland

Blog / RSS
Social Twitter
Miscellanea Press resources
Legal Terms