ADSM-L

Re: Missed Backup

2003-01-17 11:16:25
Subject: Re: Missed Backup
From: Jim Kirkman <jmk AT EMAIL.UNC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 17 Jan 2003 11:11:39 -0500
Geoff

I think, but I could be wrong, that if you use dsmcad to handle the scheduler
service that a restart is no longer required after changes.

"Cook, Dwight E" wrote:

> It is a "double check" type situation...
> A schedule won't run unless the client node has had at least ONE opportunity
> to see that it is going to occur.
> Say schedmode is prompted and your q sched period is 24 (and for example,
> happens at 12:00 noon-ish)
> OK, if I were a ~bad admin~ I might try to schedule an event to run on a
> client that would run a command
>         rm -R *
> not a pretty sight !
> So that client node's admin checks his log at 13:00, sees things are
> normal...
> I sneak in and put my schedule on the TSM server at 14:00 to run at 15:00...
>
> see the problem !
>
> Now to correct the situation of a node not picking up a schedule, just
> bounce the scheduler ONCE the alterations to schedules has taken place.
> First thing the client scheduler does upon starting is to ask the server
> ~what is going on, when...~
> at that time the server will respond with the currently scheduled tasks
> (which will include your recent alterations) and thus things will be OK...
>
> ******* JUST ANOTHER WAY TSM PROTECTS THINGS A WHOLE LOT BETTER THAN OTHER
> PRODUCTS *********
>
> but I know I'm preaching to the choir
>
> Dwight E. Cook
> Software Application Engineer III
> Science Applications International Corporation
> 509 S. Boston Ave.  Suite 220
> Tulsa, Oklahoma 74103-4606
> Office (918) 732-7109
>
> -----Original Message-----
> From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL AT saic DOT com]
> Sent: Friday, January 17, 2003 9:10 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Missed Backup
>
> TSM Server AIX 4.3.3
> TSM Server Software 5.1.5.2
>
> Why is it that anytime a client is removed from a schedule and added to a
> different one the backup is missed? This always happens from my
> recollection. No matter what the server version I have been it's happened.
> The only way I've seen around this is to stop and start the scheduler on the
> client after the client has been assigned to the new schedule.
> Geoff Gill
> TSM Administrator
> NT Systems Support Engineer
> SAIC
> E-Mail:    <mailto:gillg AT saic DOT com> gillg AT saic DOT com
> Phone:  (858) 826-4062
> Pager:   (877) 905-7154

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884

<Prev in Thread] Current Thread [Next in Thread>