About schedules
You can perform automatic, unattended activities on specified backup sets when you create a schedule and assign backup sets to that schedule. A schedule is composed of details that define when unattended backups will be performed.
NOTE: The Backup Schedules tab allows Administrators and Backup Operators to monitor and adjust the scheduled backup load on DS-Client.
You can limit the number of scheduled activities that can run concurrently by configuring the
MaxSessions (Windows) or
MaxSessions Number (Linux) advanced parameter. This is useful if you are running simultaneous backups and some data is being backed up using a slower connection. Similarly, if there are too many backup sets using the same schedule, this will decrease the efficiency of DS-Client. For more information, see
“Configuring the advanced settings”).
NOTE: For Grid DS-Clients, the limit will be the sum of all the MaxSessions parameters from all running nodes.
How scheduled operations start and run
DS-Client checks for scheduled operations that are to be triggered 24 hours a day. If a scheduled activity is started but cannot finish because the connection to DS-System cannot be established or is lost, the DS-Client retries thee times, at a five-minute intervals (by default) to resume or initiate the connection. To configure the number of attempts and the interval between retries, verify the DS-Client’s
Attempt to reconnect setting (see
“Configuring the parameter settings”). If the scheduled operation is missed for this reason, an attempt will be made to perform it at the next scheduled time. For example, a backup scheduled to take place every day at 14:00 will retry the 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. For more information, see
“Configuring the advanced settings”.
Scheduling from a DS-User in a different time zone
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 the time zone of the DS-User. For example:
• A DS-User in the Pacific Standard time zone connects at 07:50 AM to a DS-Client in the Eastern Standard time zone (10:50 AM). The DS-User (PST) sets the DS-Client (EST) schedule to 07:51 AM. On DS-Client, that 07:51 AM PST schedule is interpreted as the corresponding current local time (10:51AM EST).
• All log times returned by DS-Client database are Eastern Standard Time.
• If the DS-User is not in the same time zone, the time is converted to the equivalent value for the time zone. For example, if a DS-User (EST) displays 10:51 AM for an activity, that same activity will show a time of 07:51 AM on a remote DS-User (PST).