Thats exactly what i noticed. If the schedule is running with scheduler
service (at command) on NT
i got no information on the ADSM server side. Only "Node XY starting. Node
XY ending".
I wrote some Unix based Scripts to get information about the server
logfiles. (select statements)
But NT is not Unix, so my scripts doesn't work there. And the grep is
terribly missing in the NT environment.
Therefore we told our implementation team to give us the path to the client
logs to check them with ITO (HP OpenView).
We extract text patterns like 'ANSXXXXXX' and tell ITO to keep an eye on it.
(I do automatically a Query actlog for the last 30 minutes,
redirecting the output in a file, then i give ITO control over that file and
track the patterns. If one meets my samplepattern ITO displays it
on the screen with different colors. depends on the action that should
happen if a pattern appear!) Thats how i check the server and client log.
I ask myself thousend times why we bougth a product that is like an empty
bottle. It only makes backups but cares not about how to handel daily
work....
> -----Ursprüngliche Nachricht-----
> Von: Leo Humar [SMTP:lhumar AT BIGPOND.NET DOT AU]
> Gesendet am: Mittwoch, 13. Oktober 1999 15:33
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: AW: Connecting Agent for Exchange and tool to check the
> logs and serv er status
>
> Have you checked if there's a "scheduler service" running on the NT
> clients.
> That could be one of the reasons why you are using "at".
> We have used the command with our scheduler in the past and found that we
> didn't get any valid reports from ADSM.
>
> Leo Humar
> LCS Pty Ltd
> lhumar AT bigpond.net DOT au
>
> No trees were killed in the sending of this message. However a large
> number of electrons were terribly inconvenienced.
>
> -----Original Message-----
> From: Roland Bender <BENDERR AT ING.BOEHRINGER-INGELHEIM DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
> Date: 13 October 1999 22:45
> Subject: AW: Connecting Agent for Exchange and tool to check the logs and
> serv er status
>
>
> I'll try that, but the 66 NT nodes uses not the adsm scheduler, they are
> running (the hell knows why) via NT schedule (at command)
> hope they are included in the query.
>
> > -----Ursprüngliche Nachricht-----
> > Von: Jordan, Chris (ELS) [SMTP:c.jordan AT ELSEVIER.CO DOT UK]
> > Gesendet am: Mittwoch, 13. Oktober 1999 14:24
> > An: ADSM-L AT VM.MARIST DOT EDU
> > Betreff: Re: Connecting Agent for Exchange and tool to check the
> logs
> > and serv er status
> >
> > Each morning I do a QUERY EVENT * * BEGINDATE=-1
> > This lists all the completed, missed and failed backups. From that list
> I
> > decide what to do next.....
> >
> > I also do a QUERY ACTLOG BEGINDATE=-1 SEARCH=error
> > and check to see if there are any major errors on the tape library or
> > anywhere.
> >
> > Cheers, Chris
> >
> > -----Original Message-----
> > From: Roland Bender [mailto:BENDERR AT ING.BOEHRINGER-INGELHEIM DOT COM]
> > Sent: 13 October 1999 12:44
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: AW: Connecting Agent for Exchange and tool to check the logs
> > and serv er status
> >
> >
> > The idea in general sounds good. But i think i am and my two partners
> are
> > responsible for backup/restore operations.
> > So if we send us the logs of all 131 Nodes that we backing up with adsm,
> > we
> > do nothing else the day as looking into
> > logfiles. Because of that i was looking for a tool that takes that part
> > for
> > me. I backing up 9 exchange Servers, up to 44 Unix clients,
> > about 66 Windows NT nodes. Several Open VMS systems. I was hoping that
> HP
> > Openview IT could take the part of collecting information
> > for me, but was a misinterpretation. ITO does not collect things by its
> > own,
> > we have to define things watched by ITO.
> >
> > I ask myself how other companies handel that. There must be a tool or
> > someting from Tivoli maybe. Well it seems that i'll have to find it.
> >
> > But thanks again
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Jordan, Chris (ELS) [SMTP:c.jordan AT ELSEVIER.CO DOT UK]
> > > Gesendet am: Mittwoch, 13. Oktober 1999 13:30
> > > An: ADSM-L AT VM.MARIST DOT EDU
> > > Betreff: Re: Connecting Agent for Exchange and tool to check the
> > logs
> > > and serv er status
> > >
> > > Sorry, I have no idea what the return code is.
> > > There might be one - as Query Client Events shows it as "completed".
> > > There might not be one - as the Activity Log doesn't indicate a
> success
> > or
> > > failure - just a started and ended line.
> > >
> > > The best place to look at are the details in the ADSM Agent log files
> on
> > > the
> > > Exchange server - and have these mailed out to the relevant people as
> a
> > > part
> > > of the backup script called by the ADSM scheduler.
> > >
> > > Cheers, Chris
> > >
> > > -----Original Message-----
> > > From: Roland Bender [mailto:BENDERR AT ING.BOEHRINGER-INGELHEIM DOT COM]
> > > Sent: 13 October 1999 12:15
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: AW: Connecting Agent for Exchange and tool to check the logs
> > > and serv er status
> > >
> > >
> > > Hi Chris ,
> > >
> > > you are right, backups are not completing correctly, i noticed that
> the
> > > full
> > > backup are not successful
> > > Therefore the incremental cannot be o.k. and the logfiles will not be
> > > deleted. Thats o.k. i think.
> > >
> > > I have to run a full backup, then the logfiles will be deleted. I
> would
> > > like
> > > to know what code exchange agent gives to
> > > adsm that the backup is right. Because i could check that code with
> ITO!
> > >
> > > Thanks Chris.
> > >
> > >
> > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Jordan, Chris (ELS) [SMTP:c.jordan AT ELSEVIER.CO DOT UK]
> > > > Gesendet am: Mittwoch, 13. Oktober 1999 13:08
> > > > An: ADSM-L AT VM.MARIST DOT EDU
> > > > Betreff: Re: Connecting Agent for Exchange and tool to check
> the
> > > logs
> > > > and serv er status
> > > >
> > > > Our version 1.1.0.0B is OK.
> > > > Is the command you typed as specified on the Exchange Server?? The
> > > actual
> > > > command is EXCDSMC and NOT EXECDSMC.
> > > >
> > > >
> > > > Are your backups actually completing correctly?
> > > > Are the relevant Exchange messages to indicate completed backups
> > present
> > > > in
> > > > the Event Viewer of the Exchange server?
> > > >
> > > > It should automatically delete the old Exchange log files - NOT all
> > the
> > > > log
> > > > files as it will start a couple more immediately the backup is
> > > completed.
> > > >
> > > > The backups are then stored in ADSM for ever - unless you delete the
> > > file.
> > > > You can use the new command introduced in 0.0B to do this
> > automatically
> > > > (see
> > > > the readme for details).
> > > >
> > > > Cheers, Chris
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Roland Bender [mailto:BENDERR AT ING.BOEHRINGER-INGELHEIM DOT COM]
> > > > Sent: 13 October 1999 11:49
> > > > To: ADSM-L AT VM.MARIST DOT EDU
> > > > Subject: Connecting Agent for Exchange and tool to check the logs
> and
> > > > serv er status
> > > >
> > > >
> > > > Hello again,
> > > >
> > > > i have some other questions to the members of this helpfull list.
> > > >
> > > > Our Server Level is:
> > > > ADSM Server for AIX-RS/6000 - Version 3, Release 1, Level
> 2.0
> > > >
> > > > First:
> > > > We use ADSM Connecting Agent for MS Exchange Version1,
> Release
> > > 1,
> > > > Level 0.0B
> > > > It seems that when a full backup is completed, the Exchange
> > > > Server
> > > > does not delete his backed up logfiles. Therefore the
> Exchange
> > > > Server run nearly out of space. I have no idea why he don't
> > > delete
> > > > his logs.
> > > >
> > > > Our backup command is the following:
> > > >
> > > > execdsmc /backup:is,full /adsmpwd:<PASSWORD>
> > > /compress:yes
> > > > /buffers:6,128
> > > >
> > > > execdsmc /backup:dir,full /adsmpwd:<PASSWORD>
> > > > /compress:yes
> > > > /buffers:6,128
> > > >
> > > > The filesystem is backed up by another script.
> > > >
> > > > The compress statement sounds strange to me, because the
> > drives
> > > > uses
> > > > hardware compression.
> > > > (3590-B1A). I think that hardware compression is much better
> > > than
> > > > the client compression. Our transferrate is 3,5 G per hour. (FDDI)
> > > > Seems to me like a bottleneck in our implementation. I'll
> have
> > > to
> > > > check that later...
> > > >
> > > > My questions concerning this:
> > > > * Is there a known bug in the ADSM Connection Agent for
> > Exchange?
> > > > * Does anybody know the returncode sended by the ADSM API to
> the
> > > > Exchange API for successful backup operation?
> > > > * Is a new Connecting Agent for Exchange available?
> > > >
> > > >
> > > > Second:
> > > > I'am looking for a kind of tool that help me getting
> > information
> > > > if
> > > > a backup is successful or not. Yes, i could search
> > > > the actlog, but than i do nothing else because of 131 Nodes.
> > At
> > > > the
> > > > moment i use HP OpenView IT. The problem is, that
> > > > ITO wants to know what it should report. I am sure others
> face
> > > or
> > > > faced the same problem.
> > > >
> > > > My questions concerning this:
> > > > * What tools are available to check the client and server logs
> > > > automatically.(Maybe Tivoli? I only know the name...)
> > > >
> > > >
> > > > Thanks to Mecki once more.
> > > >
> > > > And thanks to all others of you.
> > > >
> > > > Yours
> > > >
> > > >
> > > > Roland Bender
> > > >
> > > > Boehringer Ingelheim Pharma KG
> > > > A Informationsverarbeitung
> > > > IT Betrieb Ingelheim
> > > > Job- und Datenservice
> > > >
> > > > Tel: 06132 / 77 - 2014
> > > > e-Mail: BenderR AT ing.boehringer-ingelheim DOT com
> > > > ===================================================================
> > > > Notice:
> > > > An electronic message is not binding on its sender.
> > > > Any message referring to a binding engagement must be confirmed in
> > > writing
> > > > and duly signed.
> > > > ===================================================================
|
