Manually removing Exchange transaction log files that are not required
Many times we need to remove transaction log files because disk space issue.
To correctly remove excess transaction log files, follow these steps:
- Stop all the databases in the storage group.
- Verify the state of each database file in the particular storage group. For information about how to verify the state of each database file, see the "Database states" section.
- Perform one of the following actions:
- If one or more of the databases are in a Dirty Shutdown or Inconsistent state, determine which transaction log files can be removed without affecting database consistency. For more information, see the "Log files" section.
- If all the databases are in a Clean Shutdown or Consistent state, you may remove all the transaction log files except for the current transaction log file. Removing the current log file when all databases are in a Clean Shutdown state will cause a reset of the log file sequence. This does not prevent databases from starting. However, a reset of the log file sequence affects the ability to roll a database forward from a previous backup if the situation occurs.
- Copy all the transaction log files that you want to remove to a different location before you permanently remove them from the transaction log hard disk. Do not permanently delete the transaction log files until you have successfully completed a full online backup of all the databases in the storage group.
If you have any queries/questions regarding the above mentioned information then please let me know.