Backup scheduling
You can inject the backup schedules using the strategies.
| Key | Parameter | Control |
|---|---|---|
| Configuration.Schedule | backup [set < set >] every < day >{,< otherDay >} at < time > for < duration > [limit bandwidth < size >] | Scheduling backups |
The parameters have the following roles and values :
- [set < set >:] : optional parameter. If not specified, CDP preferences will apply to all selections.
- day et otherDay : week day(s) where to run the backup tasks. In English, shortened :
- mon : monday
- tue : tuesday
- wed : wednesday
- thu : thursday
- fri : friday
- sat : saturday
- sun : sunday
- time : start time of the backup task. 24 hours format (For example : 1, 12:45, 8:15, 23, etc...)
- duration : maximum backup duration. 24 hours format (par exemple : 2, 6:30, 12, etc...)
- size : bandwidth limit for the current schedule, in bytes per second. You can express the speed in kilobytes per second by adding "k" after the value.
Delayed triggering
Since Arx One Backup version 8.1 , scheduled backups can be triggered using a random delay. The default value is 15 minutes, which means that the backup will start 15 minutes maximum after the scheduled time. This maximum delay can be changed using a strategy as follow :
| Key | Parameter | Control |
|---|---|---|
| Configuration.BackupRandomDelay | < delay > | Defines the maximum delay |
- delay : Maximum triggering delay, expressed in minutes.
Example
You need to perform your backup from monday to friday from 12h30 to 13h30 with a bandwidth limit of 50 kB/s. Then you will backup friday night from 20h to 8h, without any bandwidth limit.
Resulting strategy :
Configuration.Schedule: backup every mon,tue,wed,thu,fri at 12:30 for 1 limit bandwidth 50 k
Configuration.Schedule: backup every fri at 20:00 for 12