5 conditions, 1 user is idle, Conditions – Acronis Backup for Windows Server - User Guide User Manual

Page 69

Advertising
background image

69

Copyright © Acronis International GmbH, 2002-2014

To view properties of an event, including the event source and event number

1. In Event Viewer, click the name of a log that you want to view—for example, Application.

Note: To be able to open the security log (Security), you must be a member of the Administrators group.

2. In the list of events in the right pane, double-click the name of an event whose properties you

want to view.

3. In the Event Properties dialog box, view the event's properties such as the event source, shown

in the Source field; and the event number, shown in the Event ID field.

When you are finished, click OK to close the Event Properties dialog box.

4.4.5 Conditions

Conditions add more flexibility to the scheduler, enabling to execute backup tasks with respect to
certain conditions. Once a specified event occurs (see the "Scheduling (p. 60)" section for the list of
available events), the scheduler checks the specified condition and executes the task if the condition
is met.

Conditions are available only when the custom backup scheme (p. 47) is used. You can set conditions for full,
incremental and differential backup separately.

The scheduler behavior in case the event occurs but the condition (or any of multiple conditions) is
not met, is defined by the Task start conditions (p. 98) backup option. There, you can specify how
important the conditions are for the backup strategy:

conditions are obligatory - put the backup task run on hold until all the conditions are met.

conditions are preferable, but a backup task run has higher priority - put the task on hold for the
specified time interval. If the time interval lapses and the conditions are still not met, run the
task anyway. With this setting, the program will automatically handle the situation when the
conditions are not met for too long and further delaying the backup is undesirable.

backup task start time matters - skip the backup task if the conditions are not met at the time
when the task should be started. Skipping the task run makes sense when you need to back up
data strictly at the specified time, especially if the events are relatively often.

Adding multiple conditions

If two or more conditions are specified, the backup will start only when all of them are met.

4.4.5.1

User is idle

Applies to: Windows

"User is idle" means that a screen saver is running on the managed machine or the machine is locked.

Example:

Run the backup task on the managed machine every day at 9PM, preferably when the user is idle. If
the user is still active by 11PM, run the task anyway.

Event: Daily, every 1 day(s); Once at: 09:00:00 PM.

Condition: User is idle.

Task start conditions: Wait until the conditions are met, Run the task anyway after 2 hour(s).

As a result,

Advertising