exchange, transaction logs
if we are deleting log files from exchange server for some reason or manually flushing the logs, which ones should we leave
recent 100 logs or 200 , how ill I know which ones to keep and which old ones to delete.
recent 100 logs or 200 , how ill I know which ones to keep and which old ones to delete.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hello,
There are different type of logs like below, which not to be delete are edb.csk, .edb, and res1 and Res 2
here find below the description and work of logs
Transaction log (.log)
These files are the repository for database operations such as creating or modifying a message. Committed operations are later written to the database itself (in an .edb file). This approach guarantees that all complete and incomplete transactions are logged to maintain data integrity in case of a service interruption. Each database has its own set of transaction logs.
Checkpoint (.chk)
These files are the repository for data that indicates when an operation is successfully saved to the database on the hard disk. Exchange 2010 uses .chk files so an instance of the ESE can automatically replay log files into an inconsistent database when recovering from a service interruption, starting with the next unwritten operation. The .chk files are placed in the same log location as the .log files.
There are different type of logs like below, which not to be delete are edb.csk, .edb, and res1 and Res 2
here find below the description and work of logs
Transaction log (.log)
These files are the repository for database operations such as creating or modifying a message. Committed operations are later written to the database itself (in an .edb file). This approach guarantees that all complete and incomplete transactions are logged to maintain data integrity in case of a service interruption. Each database has its own set of transaction logs.
Checkpoint (.chk)
These files are the repository for data that indicates when an operation is successfully saved to the database on the hard disk. Exchange 2010 uses .chk files so an instance of the ESE can automatically replay log files into an inconsistent database when recovering from a service interruption, starting with the next unwritten operation. The .chk files are placed in the same log location as the .log files.
ASKER