Exchange 2010 Hard Drive Space Issues
-
Just open Windows Explorer and look at your log directory. If you are not using an Exchange aware backup program then your logs are not getting purged.
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
@brianlittlejohn Do you know of a powershell command to check this? I could be sitting here for 30 minutes waiting for it to calculate the space
If it is taking that long to calculate the logs folder space, then that is the problem. You probably have tens of thousands of little log files there and they arent being truncated daily.
-
@momurda I'll check on it. Thanks
-
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.
-
@sully93 Thanks
-
This does seem to be the issue. What backup solution should we be moving to? Veeam?
-
What are you using now? Are yopu sure it is configured correctly for exchange?
-
@momurda said in Exchange 2010 Hard Drive Space Issues:
What are you using now? Are yopu sure it is configured correctly for exchange?
Everything here is inherited. They used Cobian backup and Windows backup.
-
2.27 TB in the logs
![😕](https://mangolassi.it/assets/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=3hrg7a1ige4 ":\")
-
@wirestyle22 said in Exchange 2010 Hard Drive Space Issues:
2.27 TB in the logs
Sure sounds like backups haven't been happening on the database.
-
That is like 1million+ log files. Cant believe your exchange is still serving mail in a timely fashion.
Cobian Backup doesnt seem to support exchange. -
Windows Backup should be able to truncate the Exchange logs.
-
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?
