ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
We've been using schedmode Polling on a Linux client. This client uses two stanzas (two nodes, two .opt files) and two dsmcad processes. Each schedule has been running once each night, as set on the server, all fine and well.
However, I wanted to do some testing that required changing the start time for one of the client schedules wherein I wanted to run it as soon as possible. There were no sessions running, and no tape drives were busy. But every time I change it (10 minutes from now, 30 minutes, 1 hour), the activity log reports that the client missed its startup window, and the backup never runs. I even stopped the dsmcad processes, changed the schedmode to Prompted, and restarted. Still no luck. For testing, I want to limit the wait time as much as possible.
Can somebody tell me if the 'Query Schedule Period' is causing the mischief? I did not set the values defined on the server, so if those have to remain as is then is there something that I can do on the client side to resolve this?
[ Here's what the server reports for `q status` ]
Schedule Randomization Percentage: 25
Query Schedule Period: 6 Hour(s)
Maximum Command Retries: Client
Retry Period: Client
Scheduling Modes: Any
[ The schedule on the server has been thus ]
Action: Incremental
Priority: 1
Start Date/Time: 03/27/2020 22:40:00
Duration: 1 Minute(s)
Maximum Run Time (Minutes): 0
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
[ The stanza in the dsm.sys file has these values ]
PASSWordaccess Generate
MANAGEDServices schedule
SCHEDMode prompted (was polling before I changed it)
queryschedperiod 1
However, I wanted to do some testing that required changing the start time for one of the client schedules wherein I wanted to run it as soon as possible. There were no sessions running, and no tape drives were busy. But every time I change it (10 minutes from now, 30 minutes, 1 hour), the activity log reports that the client missed its startup window, and the backup never runs. I even stopped the dsmcad processes, changed the schedmode to Prompted, and restarted. Still no luck. For testing, I want to limit the wait time as much as possible.
Can somebody tell me if the 'Query Schedule Period' is causing the mischief? I did not set the values defined on the server, so if those have to remain as is then is there something that I can do on the client side to resolve this?
[ Here's what the server reports for `q status` ]
Schedule Randomization Percentage: 25
Query Schedule Period: 6 Hour(s)
Maximum Command Retries: Client
Retry Period: Client
Scheduling Modes: Any
[ The schedule on the server has been thus ]
Action: Incremental
Priority: 1
Start Date/Time: 03/27/2020 22:40:00
Duration: 1 Minute(s)
Maximum Run Time (Minutes): 0
Schedule Style: Classic
Period: 1 Day(s)
Day of Week: Any
[ The stanza in the dsm.sys file has these values ]
PASSWordaccess Generate
MANAGEDServices schedule
SCHEDMode prompted (was polling before I changed it)
queryschedperiod 1