Exchange Server Forums

Event ID 225

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Information Stores >> Event ID 225

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Event ID 225 - 3.Aug.2006 8:06:37 AM

Keefy

Posts: 3
Joined: 3.Aug.2006
Status: offline

Hi,

I was wondering if anyone knows how to fix this error I am getting in the event logs on for our mail server.

Source: ESE
Category: Logging/Recovery
Event ID: 225

Information Store (5832) 26aa13df-71c0-4561-a05d-15fbbf38c6a8: No log files can be truncated.

Basically we had to move a large amount of mailboxes to a new mailbox store the other night and the transaction logs filled up the log drive they were stored on and all the mailbox stores dismounted. I changed the transaction log location in System Manager to a bigger drive and mounted all the mailbox stores and continued to move the mailboxes without a problem.

Once the moving had been completed we ran a backup that completed successfully on the new mailbox stores but I noticed this error in the eventlogs. The transaction logs are not being truncated after the backups and are quickly filling up the new drive they are on. This was working fine before the work we did the other night.

I am very new to Exchange so I apologise if the above info doesn't make much sense. I didn't find much information on this error on the net and Microsoft's link from the eventlog is not very helpfull. I was wondering if anyone has come across this problem before. Any help will be much appreciated.

Thanks

Post #: 1

Featured Links*

RE: Event ID 225 - 3.Aug.2006 11:14:05 PM

Lancy

Posts: 222
Joined: 24.Feb.2006
Status: offline

Since you moved mailboxes from one store to another the log files growth is expected.

what backup software do use? did you do a full backup?

Try backing up again and the log files should get truncated.

There are some backup software which take snap shot and those software dont truncate the log files until they are committed to database. (We use snapmanager for exchange for example).

(in reply to Keefy)

Post #: 2

RE: Event ID 225 - 4.Aug.2006 1:24:45 AM

Keefy

Posts: 3
Joined: 3.Aug.2006
Status: offline

Hi Lancy,

We use HP Data Protector as our backup software. We do a full backup on the databases and it completes successfully and have tried a number of backups on it but still getting the truncating errors.

The message we usually get before that is: Starting the backup of log files (range E:\Exchsrvr\MDBDATA\E001D93A.log - E:\Exchsrvr\MDBDATA\E001D93A.log). or something similar.

How can you check if the log files are committed to the database. I checked the checkpoint file and it was only the last 10-15 log files that seemed to be needed. Does this mean that all the other transaction logs have already been committed to the database?

Cheers

(in reply to Keefy)

Post #: 3

RE: Event ID 225 - 4.Aug.2006 3:29:02 PM

Lancy

Posts: 222
Joined: 24.Feb.2006
Status: offline

do you see events in eventviewer regarding start of backup, progress and finish?
do run a nt backup and save it to a disk on server and move it somewhere else once done. check if the log files truncates. make sure you have enough free space to backup the database.

(in reply to Keefy)

Post #: 4

RE: Event ID 225 - 11.Aug.2006 1:53:43 AM

Keefy

Posts: 3
Joined: 3.Aug.2006
Status: offline

Hi Lancy,

I solved this problem earlier on in the week and thought I better post what was causing it. I guess I better start from the beginning. The reason we were moving a whole lot of mailboxes was that one of the mailbox stores got corrupted after a raid failure and wouldn't backup. This happened about a year ago and reading the incident report from the previous Exchange Admin he had a whole lot of troubles trying to repair the database and restoring it etc so in the end he created a new mailbox store and manually moved them.

I don't know if this is a good way of doing this but it copied the mailboxes across leaving the corruption behind and was recommended by my boss to do it again this way. The problem was when I finished copying the mailboxes I didn't delete the corrupted store. There were uncommitted transaction logs for that database so Exchange was basically saying I cannot truncate the logs because of this. As soon as I deleted the old corrupted store and ran a backup the transaction log files truncated successfully.

Anyway thanks for you suggestions.

(in reply to Lancy)

Post #: 5