Michels,
First, an observation. I noticed that you listed that
you were at TDP for Exchange 1.1.1.0. You need to change
this as soon as possible. If you are going to stay with
version 1, then you must be running 1.1.1.01.
The fixtest is available at the standard FTP site.
You must have this fix on to guarantee good backups.
Also, you could go to version 2 (just released in March)
and gain the benefits like full TSM policy management
and Exchange 2000 support.
Back to your question...
Please query your TSM server activity log before, during,
and after the failure. TDP for Exchange will log
events to the TSM server activity log that states
whether the backups succeeded or failed.
Here is an example I did with version 2:
----------------------------------------------------------------------------
05/09/2001 08:38:51 ANE4991I (Session: 6, Node: KEYWEST) TDP MSExchgV2 NT
ACN3514 TDP for Microsoft Exchange: Starting backup
for
server KEYWEST.
05/09/2001 08:38:51 ANE4991I (Session: 6, Node: KEYWEST) TDP MSExchgV2 NT
ACN3500 TDP for Microsoft Exchange: Starting full
backup
of First Storage Group from server KEYWEST.
05/09/2001 08:38:52 ANR0522W Transaction failed for session 6 for node
KEYWEST
(TDP MSExchgV2 NT) - no space available in storage
pool
MARYPOOL and all successor pools.
----------------------------------------------------------------------------
Version 1 also did logging when the backups succeeded or failed.
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
"It's a beautiful day. Don't let it get away." -- Bono
Michel Engels
<Michel.Engels@DE To: [EMAIL PROTECTED]
VOTEAM.BE> cc:
Sent by: "ADSM: Subject: TDP Exchange gives out of
storage
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
05/09/2001 07:17
AM
Please respond to
"ADSM: Dist Stor
Manager"
I am testing the TDP for Exchange in an environment. Everything works fine.
We
can do full, incr backups. We do save the backups directly to a VTS atached
to
the Mainframe. Now the number of scratch tape defined for the storagepool
has
reached the maximum. I can add some tapes but my problem is the message
that the
server is out of storage (ANS1329S) is only trapped on the client and not
on the
server. The batch can give an %errorlevel% = 306 and the excdsm.log does
show
the message but the actlog does not show the problem.
Is there any possibility to send this message to the server? Do I have to
install some mail uitility on the client to be able to inform the people
concerned about the fact that the backup in not complete?
TSM Client 3.7.2 on WinNT
TDP for Exchange V1.1.1.0
TSM Server V3.7.1 on OS390
M Engels
