Schedule Randomization.
Q STAT and it's in the middle
On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote:
Date: Tue, 18 Apr 2006 09:19:56 -0600
From: Andrew Raibeck [EMAIL PROTECTED]
Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Schedule start delayed
PROTECTED]
Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Schedule start delayed
It would certainly help to see some more specifics. For example, the
dsmsched.log file for one of the clients in question that did not kick
off
when expected
, 2006 6:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Schedule start delayed
Well, of course it appears in the QUERY STATUS output. But that does not
change the fact that randomization has no bearing when SCHEDMODE PROMPTED
is being used, which is what Geoff says he is using. Randomization affects
Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
On Behalf Of Gill, Geoffrey L.
Sent: dinsdag 18 april 2006 7:13
To: ADSM-L@VM.MARIST.EDU
Subject: Schedule start delayed
I'm trying to remember what it is about a backup schedule
that, even though
scheduled for say 8PM
- Geoff Gill wrote: -
I'm trying to remember what it is about a backup schedule that,
even though scheduled for say 8PM, does not kick off right away,
nodes show pending for some time. I've been comparing the 5.2 and
5.3 server settings but can't find any obvious differences, yet
the 5.2
It would certainly help to see some more specifics. For example, the
dsmsched.log file for one of the clients in question that did not kick off
when expected, just to verify that, for sure, it is using prompted
scheduling; and the activity log from the scheduled start time and on, to
see what the
I'm trying to remember what it is about a backup schedule that, even though
scheduled for say 8PM, does not kick off right away, nodes show pending for
some time. I've been comparing the 5.2 and 5.3 server settings but can't
find any obvious differences, yet the 5.2 server kicks off each schedule
