Acronis Backup & Recovery 10 Server for Windows Manuale Utente
83
Copyright © Acronis, Inc., 2000-2010
2. Days: Last. The task will run on the last day of every month despite its actual date.
3. Once at: 10:00:00 PM.
4. Effective:
3. Once at: 10:00:00 PM.
4. Effective:
From: empty.
To: empty.
To: empty.
This schedule is widely used when creating a custom backup scheme. The "Last day of every month"
schedule is added to the full backups, while the differential backups are scheduled to be performed
once a week and incremental on workdays. For more details, see the Monthly full, weekly
differential, and daily incremental backups plus cleanup example in the Custom backup scheme (p.
121) section.
schedule is added to the full backups, while the differential backups are scheduled to be performed
once a week and incremental on workdays. For more details, see the Monthly full, weekly
differential, and daily incremental backups plus cleanup example in the Custom backup scheme (p.
121) section.
"Season" schedule
Run the task on all workdays during the northern autumn seasons of 2009 and 2010. During a
workday, the task is performed every 6 hours from 12 AM (midnight) till 6 PM.
workday, the task is performed every 6 hours from 12 AM (midnight) till 6 PM.
The schedule's parameters are set up as follows.
1. Months: September, October, November.
2. On: <all> <workdays>.
3. Every: 6 hours.
2. On: <all> <workdays>.
3. Every: 6 hours.
From: 12:00:00 AM Until: 06:00:00 PM.
4. Effective:
From: 08/30/2009. Actually the task will be started on the first workday of September. By setting
up this date we just define that the task must be started in 2009.
To: 12/01/2010. Actually the task will end on the last workday of November. By setting up this
date we just define that the task must be discontinued in 2010, after autumn ends in the
northern hemisphere.
up this date we just define that the task must be started in 2009.
To: 12/01/2010. Actually the task will end on the last workday of November. By setting up this
date we just define that the task must be discontinued in 2010, after autumn ends in the
northern hemisphere.
Several monthly schedules for one task
In the case when the task needs to be run on different days or weeks with different time intervals
depending on the month, consider adding a dedicated schedule to every desired month or several
months.
depending on the month, consider adding a dedicated schedule to every desired month or several
months.
Suppose that the task goes into effect on 11/01/2009.
During northern winter, the task runs once at 10PM on every workday.
During northern spring and autumn, the task runs every 12 hours on all workdays.
During northern summer, the task runs every first and fifteenth of every month at 10 PM.
Thus, the following three schedules are added to the task.
First schedule
1. Months: December, January, February.
2. On: <All> <All workdays>
3. Once at: 10:00:00 PM.
4. Effective:
2. On: <All> <All workdays>
3. Once at: 10:00:00 PM.
4. Effective:
From: 11/01/2009.
To: not set.
To: not set.