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=FCngliche 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
>=20
> 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.
>=20
>=20
> Are your backups actually completing correctly?
> Are the relevant Exchange messages to indicate completed backups =
present
> in
> the Event Viewer of the Exchange server?
>=20
> 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.
>=20
> 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).
>=20
> Cheers, Chris
>=20
>=20
> -----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
>=20
>=20
> Hello again,
>=20
> i have some other questions to the members of this helpfull list.
>=20
> Our Server Level is:
> ADSM Server for AIX-RS/6000 - Version 3, Release 1, Level 2.0
>=20
> 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.
>=20
> Our backup command is the following:
>=20
> execdsmc /backup:is,full /adsmpwd:<PASSWORD> =
/compress:yes
> /buffers:6,128
>=20
> execdsmc /backup:dir,full /adsmpwd:<PASSWORD>
> /compress:yes
> /buffers:6,128
>=20
> The filesystem is backed up by another script.
>=20
> 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...
>=20
> 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?
>=20
>=20
> 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.
>=20
> My questions concerning this:
> * What tools are available to check the client and server logs
> automatically.(Maybe Tivoli? I only know the name...)
>=20
>=20
> Thanks to Mecki once more.
>=20
> And thanks to all others of you.
>=20
> Yours
>=20
>=20
> Roland Bender
>=20
> Boehringer Ingelheim Pharma KG
> A Informationsverarbeitung
> IT Betrieb Ingelheim
> Job- und Datenservice
>=20
> Tel: 06132 / 77 - 2014
> e-Mail: BenderR AT ing.boehringer-ingelheim DOT com
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 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.
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
|
