全备份失败后,如何手工清除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 
Back to the top

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

相关实践学习
【涂鸦即艺术】基于云应用开发平台CAP部署AI实时生图绘板
【涂鸦即艺术】基于云应用开发平台CAP部署AI实时生图绘板
相关文章
|
Linux Shell 数据安全/隐私保护
CentOS忘记密码重置密码教程
CentOS忘记密码重置密码教程
|
SQL Oracle 安全
Oracle11g更改数据库名(详细教程)
Oracle11g更改数据库名(详细教程)
578 1
|
存储 持续交付 虚拟化
|
监控 安全 Apache
构建安全的URL重定向策略:确保从Web到App平滑过渡的最佳实践
【10月更文挑战第2天】URL重定向是Web开发中常见的操作,它允许服务器根据请求的URL将用户重定向到另一个URL。然而,如果重定向过程没有得到妥善处理,可能会导致安全漏洞,如开放重定向攻击。因此,确保重定向过程的安全性至关重要。
578 0
|
供应链 安全 大数据
区块链与大数据:重构未来世界的密码
在科技飞速发展的时代,大数据被誉为“未来的石油”,区块链则被称为“信任的机器”。两者结合,将如何重塑世界?本文解析区块链与大数据的核心特性——区块链的去中心化、安全透明与大数据的海量、多样、实时价值;展示其在金融、供应链、医疗、交通等领域的应用场景;并展望未来跨界融合、信任重构、智能化发展以及隐私保护的趋势,预示着一个高效可信的新时代的到来。
937 1
|
存储 SQL 关系型数据库
MySQL存储过程与触发器:提升数据库操作效率与数据一致性
本文深入探讨了MySQL数据库中的存储过程与触发器,通过丰富的代码示例,详细介绍了存储过程的定义与调用、参数与变量的应用,以及触发器的创建、使用和实际案例。存储过程作为预定义的一组SQL语句,能够提高数据库操作的效率,实现数据逻辑和复杂计算。同时,触发器作为在特定事件触发时自动执行的SQL语句,能够保障数据一致性和逻辑完整性。通过代码实例,读者将了解如何创建、调用存储过程,如何利用参数和变量进行数据处理,以及如何创建触发器并应用于实际场景。这些技术将使读者能够在数据库管理中更高效地进行操作和保障数据的完整性,为应用程序提供可靠的数据支持。
1369 0
|
Web App开发 负载均衡 安全
浏览器如何验证SSL证书及如何查看网站的证书
浏览器如何验证SSL证书及如何查看网站的证书
浏览器如何验证SSL证书及如何查看网站的证书
|
消息中间件 缓存 负载均衡
这些年背过的面试题——分布式篇
本文是技术人面试系列分布式篇,面试中关于分布式都需要了解哪些基础?一文带你详细了解,欢迎收藏!
这些年背过的面试题——分布式篇
|
小程序
【微信小程序】全局样式、局部样式、全局配置
【微信小程序】全局样式、局部样式、全局配置
1093 0
|
监控 关系型数据库 MySQL
CentOS8.5下安装部署开源监控系统Zabbix 6.0LTS
CentOS8.5下安装部署开源监控系统Zabbix 6.0LTS
1376 0
CentOS8.5下安装部署开源监控系统Zabbix 6.0LTS