Справочник Пользователя для Acronis backup recovery 10 workstation
Copyright © Acronis, Inc., 2000-2009
99
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.
•
Condition: Fits time interval, from 06:00:00 PM until 11:59:59 PM.
In this case, whether and when the task will run depends on the task start conditions:
•
If the task start conditions are Skip the task execution, the task will never run.
•
If the task start conditions are Wait until the conditions are met and the Run the task anyway
after check box is cleared, the task (scheduled to run at 3:00 PM) will start at 6:00 PM—the time
when the condition is met.
after check box is cleared, the task (scheduled to run at 3:00 PM) will start at 6:00 PM—the time
when the condition is met.
•
If the task start conditions are Wait until the conditions are met and the Run the task anyway
after check box is selected with, say, the 1 Hour waiting time, the task (scheduled to run at
3:00 PM) will start at 4:00 PM—the time when the waiting period ends.
after check box is selected with, say, the 1 Hour waiting time, the task (scheduled to run at
3:00 PM) will start at 4:00 PM—the time when the waiting period ends.
5.5.4. User logged off
Applies to: Windows
Enables to put a backup task run on hold until all users log off from Windows on the managed
machine.
machine.
Example
Run the backup task at 8 PM on the first and third Friday of every month, preferably when all users
are logged off. If one of the users is still logged on at 11 PM, run the task anyway.
are logged off. If one of the users is still logged on at 11 PM, run the task anyway.