XADM: Log Files Generated During Backup with Circular Logging

 Last reviewed: February 12, 1998
Article ID: Q177794
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0, 5.0

SYMPTOMS

This problem occurs when you are running Microsoft Exchange Server with circular logging enabled. Log files may be generated during an online backup and may not be removed after the online backup is complete.

STATUS

Microsoft has confirmed this to be a problem Microsoft Exchange Server version 4.0. We are currently researching this problem and will post more information here in the Microsoft Knowledge Base as it becomes available.

Microsoft has confirmed this to be a problem Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K

MORE INFORMATION

During an online backup, multiple log files may be generated even if circular logging is enabled. This will occur during times of heavy use. This can result in more than four log files being generated and used, even with circular logging enabled. In Microsoft Exchange Server version 5.5, these log files are removed after the backup is complete. In Microsoft Exchange versions 4.0 and 5.0, these log files are not removed after the backup has completed. 

Keywords          : kbbug5.00 kbfix5.00.sp2 XADM kbusage
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbpatch

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.