Link to home
Start Free TrialLog in
Avatar of Daniel Bryan
Daniel BryanFlag for United States of America

asked on

Exchange 2013 disk is out of space

Hello -
I have an exchange 2013 server running in hyper-v with over a TB of disk space allocated to it.  In the last month it has maxed out on space causing it to go into a critical condition.  I removed the old mailboxes and we are now down to 9 mailboxes.  I can't find out what is using up all the rest of the space.  I need the space back to reclaim it and free it up.  
Any tips and tricks to help with it?
FYI - VSS is not running and according to the single mailbox database size is only 130GB large.
Avatar of timgreen7077
timgreen7077

What's out of space? Is it the system drive or the DB drive or what?
Did you scan the C: drive with tools like Treesizes https://www.jam-software.com/treesize_free/ or winderstat https://windirstat.net/ ?

This will tell you exactly what is taking up space.

Also have ever run cleanmgr.exe ? You need Desktop Experience installed first from Server Manager. This will remove old superseded windows updates.

Also, try this command
dism /online /cleanup-image /spsuperseded
It removes old updates as well.

-Pat
ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Also, are you backing up the server with an exchange aware backup that would be clearing the logs?
if you are talking about exchange database drive issue,
By simply moving mailboxes space cannot be reclaimed, you need to move those mailboxes to different database and altogether on new volume and then purge old database, this will reclaim all whitespace
Avatar of Daniel Bryan

ASKER

I've done the moving of databases, which is why the mailbox database is at 130GB, which is accurate with evaluating current mailbox usage.  
I downloaded treesize last night to find the nitty-gritty information.  The server is 1.1TB of diskspace and currently only  have 20GB of space left, after I deleted the temp files and purged the deleted mailboxes.  
I should easily have 500GB plus of free space on the server.  
I will look at the article and see if that helps.  

Thanks so far for the input hopefully the ones I haven't tried work or get some more back.
You seem to be ignoring Mahesh's comment and by your last comment, it sounds very much to me like he's right - Maybe we're both wrong, but it SOUNDS like you believe that the Exchange Database file should have shrunk after deleting the mailboxes - it does not.  Further, if you didn't adjust your deleted item retention time prior to deleting them, they aren't actually deleted yet.  So running ESEUTIL to defrag and compact the database may not appear to work.  You're probably better off creating a new database and then moving mailboxes to it.  The database should grow by the size of the mailboxes you move and those you don't will be deleted when you delete the old database (though I don't recall if Exchange will complain if the deleted item retention isn't up for those items).
https://kx.cloudingenium.com/microsoft/servers/exchange/compact-size-exchange-mailbox-database/
Sorry - for the misunderstanding, I actually already created a new exchange database and moved the current mailbox users to this database and deleted the old database and purged.  Everything above, but the treesize, was what I had already tried during this process.  I haven't ignored anyone's suggestion, they were already tried before posting here.  Which is why I was asking for other ideas, because everything mentioned were the top google solutions in this process.  
I'm hoping its just some log issues that are for some reason taking up so much diskspace.
I will keep researching and try the tree size tool, along with the articles to verify they are 100% identical in process of what was already tried.
You didn't mention that you tried what has been suggested - if you want more helpful answers, you generally need to include what you've done in the question or we're all wasting time telling you what you've already done.

I would suggest my article be read first though... When you run disk sizing utilities, you don't always get complete information due to security settings on the system.  My article describes one way you can get more accurate results (only way I know of, short of altering permissions of the entire drive which would not be advisable).
Understand the Puzzling Mathematics of ‘White Space’ in Exchange Database:
https://www.lepide.com/blog/the-puzzling-mathematics-of-white-space-in-exchange-database/
If you are backing up the db, log won't be an issue. If not, then enable circular logging now. That will clear the logs for now. However, it is not recommended in long run.
ou can create a new database and move all users to the new database and delete the old one.

This way you can save the white space with zero downtime.

Create database

Delete the old one after moving all mailboxes including system mailboxes:
http://exchangeserverpro.com/exchange-2013-database-removal-error-this-mailbox-database-contains-one-or-more-mailboxes/


To get an accurate representation of the amount of white space in an Exchange database we need to use ESEUTIL /MS.
You can refer to the following blog to execute the action:

https://blogs.technet.microsoft.com/rmilne/2013/08/20/how-to-check-database-white-space-in-exchange/
As mentioned in another reply, already created a new database and moved the active clients to the new database, so far found about 100GB of log reports (related bug with iphones and exchange), that freed up about 30GB.  Still trying to find what is using 600GB of whitespace on the drive.
I appreciate everyone's responses so far,Bought some time with the freed up 30GB, but only increased 5GB over weekend.  Will be back tackling this at end of week.
Is this server having RAID? If yes, unhide folder view option. check system folder in that drive. You might need to take permission for that folder and check what is the size.
After using the file tree program, I was able to find almost 400GB of logs taking up space.  I was able to apply the patch regarding the issue with exchange 2013 and iPhones to reduce the log from expanding again.  
Thank for everyone's input, even the duplicate suggestions
Closing this question. Marking Lee as the best answer. Let me know, if anyone object.