全备份失败后,如何手工清除exchange日志文件,附微软KB

本文涉及的产品
日志服务 SLS,月写入数据量 50GB 1个月
简介:

Exchange如果不采用循环日志,在成功实现全备份前,将产生大量DB日志。当磁盘性能比较差时,Exchange将延缓日志提交到数据库。因此这部分日志绝对不能删除,否则DB会有问题。而那些已经提交的db的log,其实可以手工delete掉(普通删除文件的方法)。当备份出现问题,磁盘容量又不够时,该方法非常有用。

以下KB就是帮助用户如何确定哪些日志已经提交,可以删除。

XADM: Using Eseutil to Determine Which Logs Have Been Committed
View products that this article applies to.
Article ID : 182961 
Last Review : October 28, 2006 
Revision : 4.3 
This article was previously published under Q182961
On This Page

SUMMARY

MORE INFORMATION

Exchange Server 5.5

Exchange 2000 Server
SUMMARY
You can use the Eseutil utility to view the contents of the checkpoint file to determine which log files have been committed to an Exchange database. 
Back to the top 

MORE INFORMATION
Exchange Server 5.5
The information in this section applies to all three Exchange Server 5.5 databases: • Dir.edb 
• Priv.edb 
• Pub.edb 
To display the Edb.chk (checkpoint) file on the screen, run the following command from a command prompt: 
eseutil /mk edb.chk | more
If you do not run eseutil from the folder where the Edb.chk file is located, you must provide the full path to the file.

In Exchange Server 5.5, there is one checkpoint file for each set of log files. There will be one Edb.chk file for the directory and one for the information store. (Priv.edb and Pub.edb share the same log files and checkpoint file.) 

The information that is displayed is similar to:    Microsoft(R) Exchange Server Database Utilities

   Version 5.5

   Copyright (C) Microsoft Corporation 1991-1997. All Rights Reserved.



   Initiating FILE DUMP mode...
      Checkpoint file: edb.chk

      LastFullBackupCheckpoint (8,615,203)
      Checkpoint (22,6485,399)
      FullBackup (8,615,203)
      FullBackup time:3/6/1998 11:52:16
      IncBackup (0,0,0)
      IncBackup time:0/0/1900 0:0:0
      Signature: Create time:2/24/1998 14:23:47 Rand:24842 Computer:
      Env (Session, Opentbl, VerPage, Cursors, LogBufs, LogFile, Buffers)
          (    168,   25200,    4440,    8400,      84,   10240,    8045)

   Operation completed successfully in 0.20 seconds.
                                
Take the first number in the parentheses for the Checkpoint field and convert it to hexadecimal. The hexadecimal number is the file name of the first uncommitted log for the appropriate directory. Circular logging works by deleting all log files with generations that are lower than the generation in the checkpoint, for example: 
Checkpoint (22,6485,399) = EDB00016.LOG 
This syntax applies for most other fields in the dump file (LastFullBackupCheckpoint, FullBackup, IncBackup, and other fields). 
Back to the top 

Exchange 2000 Server
In Exchange 2000, there is one checkpoint file for each storage group and one for the directory. When you try to identify the last committed log file for a storage group, note that the storage group prefix applies to the checkpoint file and to all of the log files. For example, the default first storage groups checkpoint file name is E00.chk, and its log files are E00xxxxxx.log (where xxxxx is the hexadecimal sequence number of the log file).

To display the Exx.chk (checkpoint) file on the screen, run the following command from a command prompt (from the Exchsrvr\Bin folder): 
eseutil /mk the_full_path_to_the_checkpoint_file
For example, you may run the following command: 
eseutil /mk "C:\Program Files\Exchsrvr\MDBDATA\E00.chk"
Note that you must use the quotation marks if there is a space in the path to the checkpoint file.

The output of this command is similar to:    Microsoft(R) Exchange Server(TM) Database Utilities
   Version 6.0
   Copyright (C) Microsoft Corporation 1991-2000.  All Rights Reserved.

   Initiating FILE DUMP mode...
         Checkpoint file: C:\Program Files\Exchsrvr\MDBDATA\E00.chk

         LastFullBackupCheckpoint: (0x0,0,0)
         Checkpoint: (0x6A,1119,3D)
         FullBackup: (0x0,0,0)
         FullBackup time: 00/00/1900 00:00:00
         IncBackup: (0x0,0,0)
         IncBackup time: 00/00/1900 00:00:00
         Signature: Create time:09/24/2001 17:10:26 Rand:522553071 Computer:
         Env (CircLog,Session,Opentbl,VerPage,Cursors,LogBufs,LogFile,Buffers)
             (    off,    202,  30300,   1365,  10100,    128,  10240,  97940)

   Operation completed successfully in 1.192 seconds.
                                
Take the first number in the parentheses for the Checkpoint field. The hexadecimal number is the file name of the first uncommitted log for the appropriate database; in this example: 
Checkpoint (0x6A,1119,3D) = E000006A.log 



本文转自9pc9com博客,原文链接:    http://blog.51cto.com/215363/808394    如需转载请自行联系原作者op

相关实践学习
日志服务之使用Nginx模式采集日志
本文介绍如何通过日志服务控制台创建Nginx模式的Logtail配置快速采集Nginx日志并进行多维度分析。
相关文章
|
25天前
|
监控 Linux 应用服务中间件
系统监控:使用日志文件 journalctl的使用
本文介绍了如何使用`journalctl`命令来监控和查看Linux系统的日志文件,包括查看特定行数、过滤日志级别、实时跟踪日志、按时间段查询日志以及日志轮换和压缩的配置。
19 2
系统监控:使用日志文件 journalctl的使用
|
19天前
|
SQL 数据库
为什么 SQL 日志文件很大,我应该如何处理?
为什么 SQL 日志文件很大,我应该如何处理?
|
25天前
|
开发工具 git
git显示开发日志+WinSW——将.exe文件注册为服务的一个工具+图床PicGo+kubeconfig 多个集群配置 如何切换
git显示开发日志+WinSW——将.exe文件注册为服务的一个工具+图床PicGo+kubeconfig 多个集群配置 如何切换
32 1
|
26天前
|
存储 监控 固态存储
如何监控和优化 WAL 日志文件的存储空间使用?
如何监控和优化 WAL 日志文件的存储空间使用?
|
21天前
|
SQL 数据库
为什么SQL日志文件很大,该如何处理?
为什么SQL日志文件很大,该如何处理?
|
2月前
|
缓存 监控 算法
分析慢日志文件来优化 PHP 脚本的性能
分析慢日志文件来优化 PHP 脚本的性能
|
2月前
|
消息中间件 存储 监控
Kafka的logs目录下的文件都是什么日志?
Kafka的logs目录下的文件都是什么日志?
78 11
|
2月前
|
Python
Python如何将日志输入到文件里
Python如何将日志输入到文件里
|
3月前
|
Java 应用服务中间件 HSF
Java应用结构规范问题之配置Logback以仅记录错误级别的日志到一个滚动文件中的问题如何解决
Java应用结构规范问题之配置Logback以仅记录错误级别的日志到一个滚动文件中的问题如何解决
|
3月前
|
数据库 Java 监控
Struts 2 日志管理化身神秘魔法师,洞察应用运行乾坤,演绎奇幻篇章!
【8月更文挑战第31天】在软件开发中,了解应用运行状况至关重要。日志管理作为 Struts 2 应用的关键组件,记录着每个动作和决策,如同监控摄像头,帮助我们迅速定位问题、分析性能和使用情况,为优化提供依据。Struts 2 支持多种日志框架(如 Log4j、Logback),便于配置日志级别、格式和输出位置。通过在 Action 类中添加日志记录,我们能在开发过程中获取详细信息,及时发现并解决问题。合理配置日志不仅有助于调试,还能分析用户行为,提升应用性能和稳定性。
48 0