Hi Ernie,
I thought this very exact thing late last night. I'm glad that you can confirm
it. I had interpreted the group resource 'level:full' as a means to guarantee
that full would always be performed. I had thought (obviously incorrrectly)
that 'skips' would override. But on hind sight, why would it.
Also thanks for the 'Force Incremental'. I've obviosly been overlooking that
one, too.
Thanks again,
/\/elson
On Thu, 22 May 2003, Bokkelkamp Ernst wrote:
> Hallo David,
>
> You may have overlooked the obvious:
>
> Why do you have "level: full;" in the group resource ? This will override any
> schedule.
> The priority is: Group Level; Group Schedule; Client Schedule.
> But there is also something else to be aware of: "force incremental: Yes;"
> This option overrides the Group Level if a full has already been performed on
> the same day.
>
> Bye
> Ernie
>
>
> -----Original Message-----
> From: David E. Nelson [mailto:david.nelson AT ni DOT com]
> Sent: Thursday, May 22, 2003 2:11 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] "skip" schedules are running
>
>
> Hi George,
>
> Good data below....
>
> On Wed, 21 May 2003, George Sinclair wrote:
>
> > Are you sure those clients are really using that schedule?
>
> Yes. I've included the info below with the unnessary bits snipped. In this
> case, this job ran this afternoon and the schedule clearly says 'skip'.
>
> Client Info:
> type: NSR client;
> name: tbox;
> server: devnull;
> archive services: Disabled;
> schedule: TBoxArchWeekend;
> browse policy: Month;
> retention policy: Month;
> directive: Unix standard directives;
> group: TBoxArchWeekend;
> save set: /u06/oracledbf;
>
> Schedule Info (with some hidden options shown):
> type: NSR group;
> name: TBoxArchWeekend;
> autostart: Enabled;
> autorestart: Disabled;
> stop now: False;
> start time: "16:00";
> last start: "Wed May 21 16:00:00 2003";
> interval: "24:00";
> force incremental: Yes;
> savegrp parallelism: 0;
> client retries: 1;
> clones: No;
> clone pool: Default Clone;
> migration clone pool: Migration Clone;
> options: ;
> level: full;
> printer: ;
> schedule: ;
> schedule time: ;
> inactivity timeout: 30;
> work list: ;
> completion: tbox, /u06/oracledbf, "succeeded:skip:save",
> "tbox:/u06/oracledbf level=skip, pool=TBoxWeekend, save as of Wed May 21 \
> 17:03:48 GMT-0500 2003",
> tbox, index, "succeeded:skip:index",
> "tbox:index level=skip, pool=TBoxWeekend, save as of Wed May 21 \
> 17:03:49 GMT-0500 2003";
>
> Group Info:
> type: NSR group;
> name: TBoxArchWeekend;
> autostart: Enabled;
> start time: "16:00";
>
>
> > The client has to specify some schedule. The default, if you don't cahnge it
> > should be 'Default'. Our clients all specify 'Default', BUT the group that
> > the client is a memeber of has its own schedule, and that will overide the
> > 'Default'.
>
> Correct. No schedule is applied to the group as shown above. We let clients
> handle the scheduling. Notice that the group "last start" says "Wed May 21
> 16:00:00 2003" (showing that it ran) and that the "completion" says the exact
> opposite - "tbox, /u06/oracledbf, "succeeded:skip:save", "tbox:/u06/oracledbf
> level=skip, pool=TBoxWeekend, save as of Wed May 21 \ 17:03:48 GMT-0500 2003".
>
> Go figure....
>
> > All our groups have their own specified custom schedules. Check the group
> > that's running and then check Customize->Groups->Details and make sure the
> > schedule listed for the group is in fact the one that it's supposed to
> > using.
>
> We don't use group schedules - though I'll try that tomorrow. But still, the
> above is not normal by any means.
>
> Regards,
> /\/elson
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
~~ ** ~~ If you didn't learn anything when you broke it the 1st ~~ ** ~~
time, then break it again.
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
