Re: Informing clients when their bac

Hello,

this exactly what we do. For every laptop, we offer adsm as Network
application (Start / Netwark Application / Backup C:\Data).

CLicking on that will start a DOS window and the command "Incr C:\Data". The
windows stays open at the end and the user can see statistics. The dsm.exe
code is on a Netware server and the dsmerror.log gets redirected to the
local C: disc.

Regards,

Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com



> -----Original Message-----
> From: Robinson, Cris [SMTP:Cris.Robinson AT LIBERTYMUTUAL DOT COM]
> Sent: Wednesday, February 24, 1999 8:49 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Informing clients when their bac
>
> DOH!
> Now why didn't I think of that!
>
> Thanks Wanda!
>
> CR
>
> __________________________________________________
> Cris Robinson
> Sr. Technical Analyst
> Enterprise Storage Management / ADSM
> Liberty Mutual Insurance
> Portsmouth, New Hampshire
> 603.431.8400.54837
> mailto:cris.robinson AT libertymutual DOT com
>
> Dilbert words of Wisdom:
> On the keyboard of life,
> always keep one finger on the escape key!
>
> > -----Original Message-----
> > From: Prather, Wanda [SMTP:PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU]
> > Sent: Wednesday, February 24, 1999 1:13 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: Informing clients when their bac
> >
> > We have also occasionally had users who complain that they can't get a
> log
> > when they push a backup from the GUI, don't know if anybody has ever
> > submitted that as a requirement to IBM.
> >
> > FWIW, for those people I recommend that they run the backup from the
> > command
> > line - you can redirect the output to a log file then, I think it is the
> > same output you would get from the scheduler.
> >
> > Then you could just give your laptop manager-type users a 1-line script
> or
> > icon to run - they wouldn't even have to open the GUI and make all those
> > mouse clicks to run a backup!
> >
> >
> >
> > > -----Original Message-----
> > > From: Robinson, Cris [SMTP:Cris.Robinson AT LIBERTYMUTUAL DOT COM]
> > > Sent: Wednesday, February 24, 1999 12:47 PM
> > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > Subject:      Re: Informing clients when their bac
> > >
> > > We are working to create an applet which will read the DSMSCHED.LOG
> for
> > > the
> > > succcess of failure of a backup and notify them regularly similiar to
> > > retrospect, which we once used also.
> > >
> > > The problem we are running into is that the ADSM programmers wrote the
> > > client so that output to this log file is sent only if the backup
> event
> > is
> > > scheduled.
> > >
> > > If a user pushes a backup, (we have 8000 laptop users who do this),
> then
> > > no
> > > log entry is created. You would think this wouldn't matter since the
> > user
> > > is
> > > pushing the backup and should know they have or have not backed up,
> > (these
> > > are mostly managers, 'nuff said). Problem is that they don't pay
> > attention
> > > and often times the backup was unsuccessful. Users, what can ya do?
> > >
> > > So we have asked the programmers to help us out with this one and
> commit
> > > all
> > > transactions to the log.
> > > We also thought of the e-mail route but we have 25,000+ clients and
> only
> > > so
> > > much network to abuse.
> > >
> > > Such an easy thing to do, right?
> > >
> > > Good luck!
> > > __________________________________________________
> > > Cris Robinson
> > > Sr. Technical Analyst
> > > Enterprise Storage Management / ADSM
> > > Liberty Mutual Insurance
> > > Portsmouth, New Hampshire
> > > 603.431.8400.54837
> > > mailto:cris.robinson AT libertymutual DOT com
> > >
> > > Dilbert words of Wisdom:
> > > On the keyboard of life,
> > > always keep one finger on the escape key!
> > >
> > > > -----Original Message-----
> > > > From: Steve Windhausen [SMTP:Steve.Windhausen AT ONONDAGA.NY DOT US]
> > > > Sent: Wednesday, February 24, 1999 11:50 AM
> > > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > > Subject:      Informing clients when their bac
> > > >
> > > > Subject: Informing clients when their backup is completed
> > > >
> > > > Eric,
> > > >
> > > > We use the query event command, for each node, and send the output
> to
> > > each
> > > > user's mailbox.  For failures, I get the output from the query event
> > > > command
> > > > with exceptionsonly set to yes.
> > > >
> > > > Steve Windhausen
> > > > County of Onondaga
> > > >
> > > > > We would like our clients (MAC and NT users) to have an easy way
> of
> > > > knowing
> > > > > if their scheduled backup has completed successfully. The product
> > they
> > > > have
> > > > > been using, Retrospect, would cause a window to pop up once the
> > backup
> > > > had
> > > > > completed. I don't want users to have to read the dsmsched.log to
> > > > determine
> > > > > if it worked or not.
> > > > > Naturally I can see centrally which schedules succeeded or failed,
> > but
> > > > we
> > > > > would like the user to also be informed.
> > > > >
> > > > > Has anyone any experience of this? How do others manage failed
> > backups
> > > > in
> > > > > large groups of users?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Eric Winters
> > > > > Corporate Computer Services EMEA
> > > > > Munich
> > > > > Germany
> > > > >
> > > > >