Scheduled Operations
Creation Date: February 10, 2006
Revision Date: May 01, 2013
Product: DS‑Client
Summary
This article provides additional information about scheduled activities on DS-Client.
See Also
How scheduled operations start and run
DS-Client checks for scheduled operations that are to be triggered 24 hours a day.
If an operation is started but cannot be completed (because the connection to DS-System cannot be established or is lost), by default, DS-Client will retry 3 times, each time at a five-minute interval, to resume or initiate the connection. To configure the number of attempts and the interval between retries (up to 60 minutes), click DS-User > Setup > Configuration > Parameters and see options in the Backup Options section. If the scheduled operation is missed for this reason, an attempt will be made to perform it at the next scheduled time (e.g. a backup scheduled to take place everyday at 14:00 will retry next day at 14:00.).
If the communication between the DS-Client and the customer's LAN fails for any reason, no attempts will be made to reconnect. The backup will stop since the DS-Client has no control over the customer's LAN.
If an activity is running at the time of a scheduled operation, and that activity prevents other operations from running, the scheduled operation will start as soon as that activity ends. By default, DS-Client will attempt to start a scheduled operation every minute for 6 hours from the (actual) scheduled start time. This interval is configurable on DS-Clients using the
ScheduleMiss parameter from DS-Client Advanced Configurations (see
“DS-Client Advanced Configurations”).
Examples:
• If Daily Admin or any other activity is running that locks the backup set, the schedule will start as soon as that activity ends.
• If the schedule is skipped for a reason other than losing connection to DS-System (e.g. DS-Client service is stopped), the schedule will start as soon as DS-Client starts functioning.
Scheduling from a DS-User in a different Time Zone
DS-User configures DS-Client in real-time, whatever time zone DS-User might be connecting from. The main point to remember is that you are configuring DS-Client.
When you connect to a DS-Client from a DS-User in a different time zone, the times returned by DS-Client are all converted to match your time zone.
For example
Pacific Time DS-User connects at 07:50AM to Eastern Standard Time DS-Client (10:50AM). Pacific Time DS-User sets Eastern Standard Time DS-Client schedule to 07:51AM. On DS-Client, that 07:51AM PST is interpreted as the corresponding current local time (10:51AM EST).
All log times returned by DS-Client are Eastern Standard Time (from its database).
If the DS-User is not in the same time zone, the time is converted to the equivalent value for the time zone. This means if an EST DS-User displays 10:51 for an activity, on a remote Pacific Time DS-User, that same activity will show a time of 07:51.