Exchange 2010 Hard Drive Space Issues
-
Windows backup is supposed to truncate logs, if it is configured correctly.
-
@sully93 said in Exchange 2010 Hard Drive Space Issues:
If a large number of logs are the problem then you can manually delete them if the database is clean.
- Dismount the database
- Run the command eseutil /MH "<databasename>.edb"
- If the state shows the database as Clean Shutdown you are good to delete the log files.
Feel free to hit me up if you need any help on this.
Never do this unless it is an absolute last resort. You can break shit.
I have had to do it in the past, but you seriously do not want to.
-
@sully93 said in Exchange 2010 Hard Drive Space Issues:
Windows Backup should be able to truncate the Exchange logs.
This is very correct. Windows Backup should do this if it is actually configured correctly and actually working.
-
If im in a pinch and know the backups I have are good, I turn on circular logging and restart the information store. Let it clean the logs, then switch it back and fix my backup issue.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
This does seem to be the issue. What backup solution should we be moving to? Veeam?
Just as an FYI the paid Veeam solution does handle this.
Veeam runs a backup on this server every 4 hours.
Last run was a noon. Here is the log directory.
-
@JaredBusch said in Exchange 2010 Hard Drive Space Issues:
@sully93 said in Exchange 2010 Hard Drive Space Issues:
Windows Backup should be able to truncate the Exchange logs.
This is very correct. Windows Backup should do this if it is actually configured correctly and actually working.
I do not have Windows Server Backup installed on a Server 2012 R2 system to provide examples.
-
We used to use Windows backup (before I was employed). Exchange 2010 on Server 2008 R2.
It will truncate the logs, but personally, I'd be looking for a permanent solution that covers this and the rest of your DR plan.If the logs are that big, then you haven't had a successful backup in a while. You're flying by the seat of your pants.
First port of call: Why isn't Windows backup working?
-
Since it's been almost a day since you posted this, how'd you go?
-
@nadnerB I informed my boss of this and he's going to be working on this during the weekend
-
I checked the
Volume Shadow-copy Serviceto verify that it was turned on. It was set to manual to I changed it to automatic. Now I'm going to check the type of Windows Backup we are running. -
It's a copy backup. That's why this has been happening for over a year. It needs to be either a full backup or incremental to truncate.
-
Your first full backup is going to take a long time.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
It's a copy backup. That's why this has been happening for over a year. It needs to be either a full backup or incremental to truncate.
There you go.
-
@momurda said in Exchange 2010 Hard Drive Space Issues:
Your first full backup is going to take a long time.
I'm expecting at least 24 hours
-
@JaredBusch said in Exchange 2010 Hard Drive Space Issues:
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
It's a copy backup. That's why this has been happening for over a year. It needs to be either a full backup or incremental to truncate.
There you go.
Thank your for your help
-
A full backup did not truncate the logs. Took 3 days.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
A full backup did not truncate the logs. Took 3 days.
The backup was taken using SQL Manager, right?
-
@travisdh1 No, windows server backup as I discussed above
-
I read this in a MS article:
"After about six hours on the phone with MS Support, the problem is related to the Microsoft Exchange Search Indexer Service. I don't know if it is a bug in Exchange or something in my design, but I had to dismount databases, stop the Exchange Information Store Service then delete catalogs from all database copies (active and passive). After restarting Exchange Information Store Service and remounting the databases the backs now truncate logs. The rep said the Microsoft Exchange Search Indexer Service wasn't allowing the Replication Service to truncate logs.
In addition to this issue I am seeing problems with the ContentIndexState, upon replica creation, being set to Crawling and never coming out. If I restart the Microsoft Exchange Search Indexer Service, the state moves to Healthy.
It appears all my issues point to the Microsoft Exchange Search Indexer Service and it's manifesting itself in different ways. My case is in the process of being escalated so I'll post back with an update. Hopefully someone else won't have to spend weeks fighting this too."
-
Definitely sounds like one possibility.
