There are months worth of these 10MB EDBxxxxx.LOG files. Is there an easy way to remove them? I can upgrade the client today to 5.1.6.7. Will the next backup cause AD to remove these old log files?
Bill -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: Tuesday, November 18, 2003 9:19 AM To: [EMAIL PROTECTED] Subject: Re: AD Circular Logging and TSM backups > Anyone have problems of this sort? The client > level is 5.1.0.1 (I know..upgrade!) Yes, you inadvertently answered your own question :-) This could be APAR IC33389 that you are experiencing. You can go to http://www.ibm.com and search on the APAR number for details. Fixed in 5.1.5 and up (I recommend latest 5.1.6 patch level). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Bill Boyer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/17/2003 16:52 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: AD Circular Logging and TSM backups I have a client that just forwarded me a note saying that the TSM client is causing problems with the active directory circular logging. here's the text he sent me: (See Microsoft Article) http://support.microsoft.com/default.aspx?scid=kb;en-us;272425&Product=win20 00 Issue: - Buildup of Active Directory log files (total size over 2 gigabytes) on system drive C:\. - Circular logging is enabled but not working correctly due to an interruption by the Tivoli Backup Client. Corrective Action: - Remove the System State Backup option from Tivoli nightly backups. - Ensure the version of Ntbackup.exe is 5.0.2195.2104 or greater. - Create a nightly scheduled Ntbackup.exe of the System State to a location on the server s local drive (Tivoli will back this up). - Check c:\winnt\ntds\ directory periodically to ensure log files are being truncated. Looking at the microsoft article, it is a problem with AD, not TSM and is supposedly fixed on SP2 for Win2k. I've searched IBM and adsm.org but didn't find any hits. I have other clients that backup Win2k AD with no problems and have actually done BMR restores. Anyone have problems of this sort? The client level is 5.1.0.1 (I know..upgrade!) and the TSM server is AIX 4.3.3 TSM 5.1.7.2. They want me to implement the -SYSTEMOBJECT and the NTBACKUP solution right away. I don't know what SP level the Win2k server is at. There is an Exclude.dir *:\...\NTDS in the client optionset. Bill Boyer DSS, Inc.
