Acronis Backup & Recovery 10 Server for Windows Manuale Utente
85
Copyright © Acronis, Inc., 2000-2010
Example:
Backing up data to the networked location is performed on workdays at 9:00 PM. If the location's
host is not available at that moment (for instance, due to maintenance work), skip the backup and
wait for the next workday to start the task. It is assumed that the backup task should not be started
at all rather than failed.
host is not available at that moment (for instance, due to maintenance work), skip the backup and
wait for the next workday to start the task. It is assumed that the backup task should not be started
at all rather than failed.
Event: Weekly, Every 1 week(s) on <workdays>; Once at 09:00:00 PM.
Condition: Location's host is available
Task start conditions: Skip the task execution.
As a result,
(1) If 9:00 PM comes and the location's host is available, the backup task starts right on time.
(2) If 9:00 PM comes but the host is unavailable at the moment, the backup task will start on the next
workday if the location's host is available.
workday if the location's host is available.
(3) If the location's host will never be available on workdays at 9:00 PM, the task never starts.
5.4.2 Fits time interval
Applies to: Windows, Linux
Restricts a backup task's start time to a specified interval.
Example
A company uses different locations on the same network-attached storage for backing up users data
and servers. The workday starts at 8AM and ends at 5 PM. Users' data should be backed up as soon
as the users log off, but not earlier than 4:30 PM and not later than 10 PM. Every day at 11 PM the
company's servers are backed up. So, all the users' data should be preferably backed up before this
time, in order to free network bandwidth. By specifying the upper limit as 10 PM, it is supposed that
the backing up of users' data does not take more than one hour. If a user is still logged on within the
specified time interval, or logs off at any other time – do not back up the users' data, i.e. skip task
execution.
and servers. The workday starts at 8AM and ends at 5 PM. Users' data should be backed up as soon
as the users log off, but not earlier than 4:30 PM and not later than 10 PM. Every day at 11 PM the
company's servers are backed up. So, all the users' data should be preferably backed up before this
time, in order to free network bandwidth. By specifying the upper limit as 10 PM, it is supposed that
the backing up of users' data does not take more than one hour. If a user is still logged on within the
specified time interval, or logs off at any other time – do not back up the users' data, i.e. skip task
execution.
Event: When logging off, The following user: Any user.
Condition: Fits the time interval, from 04:30:00 PM until 10:00:00 PM.
Task start conditions: Skip the task execution.
As a result,
(1) if the user logs off between 04:30:00 PM and 10:00:00 PM, the backup task will start immediately
following the logging off.
following the logging off.
(2) if the user logs off at any other time, the task will be skipped.
What if...
What if a task is scheduled to be executed at a certain time and this time is outside the specified time
interval?
interval?
For example:
Event: Daily, Every 1 day(s); Once at 03:00:00 PM.