The fix is currently planned for the fall (September/October-ish).
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Rushforth, Tim" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/04/2002 12:26
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: W2K Active Directory backup and edb000*.log files
accumulatin g
Does this apply to 5.1.1 client?
Any estimate when a fix will be available?
Thanks,
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Jim Smith [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 20, 2002 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: W2K Active Directory backup and edb000*.log files
accumulating
Alex,
This is being addressed in APAR IC33389 - TSM ACTIVE DIRECTORY BACKUP NOT
TRUNCATING LOGS
Thanks
J.P. (Jim) Smith
TSM Development
I'm backing up a W2K Domain Controller with the 4.2.1.30 client to a
4.2.1.15 server. This includes the "domain systemobject", i.e. Active
Directory. Recently I found a huge bunch of old transaction log files in
the NTDS directory: edb00001.log to edb0003e.log 10MB each. Each one was
created when TSM backed up ADS. After 60 daily backups, I got of 600MB
of these.
When I run ntbackup.exe to make a systemstate backup these log files get
erased, only the last one remained. But when I make the backup with TSM,
the log files stay and accumulate.
I cannot believe that this behaviour of TSM works as designed, because I
would have to delete the older logfiles manually after some time or use
a postschedulecmd to delete edb0*.log, which I would consider not a
clean solution. I have not found a dsm.opt option to change the client's
behaviour, and I have tried two other clients (4.2.1.20 and .32) which
had similar behaviour.
Does anybody know what's up with that issue? I assume everybody who is
backing up Active Directory via the "domain systemobject" on a Domain
Controller has this problem. But with today's gigabytes of disk space
you may have not taken notice of that yet.
Tschau
Alex
