Join Percona’s, Architect, Manjot Singh as he presents Database Backup and Recovery Best Practices (with a Focus on MySQL) on Thursday, July 27, 2017 at 11:00 am PDT / 2:00 pm EDT (UTC-7). In the case of a failure, do you know how long it will take to restore your database?
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Exchange 2000 stuck at 16GB
Posted on 2009-04-07
I have a SBS2000 running Exchange 2000, yesterday it hit the 16GB limit and since then I had nothing but problems with it.
I first did the registry trick and this allows the workstation to connect, I then archived 3GB off the server, but still the EDB shows 16.1GB in size, I then tried eseutil /p followed by eseutil /p with same result, I did a reboot just in case, I check the Mailboxes in ESM and this shows adding all users comes to just over 12GB (only 7 users), yet I cant get Exchange to free up the space so I can mount the server correctly as it stays at 16.1GB, hence shutting down the IS.
When I ran eseutil /p it came back with over 100 unknown errors but I managed to restored an image from yesterday to a fresh test server and it show the same errors yet the server were still working, I could use the spare test server as its almost identical minus this morning emails, but the EDB on the restored server showing 15.9GB so its a matter of minutes before I get hit with the same thing.
Would be most grateful for any help on this one urgently as I been doing this for over 8 hrs non-stop.
I first did the registry trick and this allows the workstation to connect, I then archived 3GB off the server, but still the EDB shows 16.1GB in size, I then tried eseutil /p followed by eseutil /p with same result, I did a reboot just in case, I check the Mailboxes in ESM and this shows adding all users comes to just over 12GB (only 7 users), yet I cant get Exchange to free up the space so I can mount the server correctly as it stays at 16.1GB, hence shutting down the IS.
When I ran eseutil /p it came back with over 100 unknown errors but I managed to restored an image from yesterday to a fresh test server and it show the same errors yet the server were still working, I could use the spare test server as its almost identical minus this morning emails, but the EDB on the restored server showing 15.9GB so its a matter of minutes before I get hit with the same thing.
Would be most grateful for any help on this one urgently as I been doing this for over 8 hrs non-stop.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
3 Comments
Try:
go into the exchange system manager (2003) and open the properties of the mailbox store, limits tab, deletion settings section.
go into the exchange system manager (2003) and open the properties of the mailbox store, limits tab, deletion settings section.
You may also try creating a second mailbox store and moving some of the mailboxes to it, but Im not sure if you can do that in your version.
The space reported in Exchange System Manager for a user's mailbox will be vastly different to what is reported in Outlook; it can't be relied upon to give a true indication of the total size of the mailboxes.
Deleting data from a mailbox will not erase it from the Exchange stores immediately; Deleted Items retention will mean the mail remains in the store until Online Maintenance removes it.
Since the database is dismounting at 16GB, I assume this is Exchange 2000 Standard Edition, where you are limited to one mailbox store. We therefore cannot simply create a new store and Move Mailboxes, per best practice; you need to mount the database temporarily, and take action to reduce its size.
The first step is to mount the database. Add the fix defined at http://support.microsoft.com/kb/813051, which temporarily extends the maximum store size to 17GB and will allow you to mount the database.
Reduce Deleted Items retention time to 0 days, then force Online Maintenance to take place. This will zero out the database pages used by the items in the dumpster.
Finally, dismount the database and run an eseutil /d - this will perform an Offline Defrag of the database, removing the white space and bringing it back below the 16GB level.
Remove the registry entry added earlier, then re-mount the store once again.
-Matt
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Microsoft has released various new features which are capable of handling various tasks. One of these tasks is ‘Migration from pop3 to Exchange Server’. Pop3 data stores various data along mailboxes like contacts, tasks, etc. So, it becomes the need…
Resolve DNS query failed errors for Exchange
- Exchange
- DNS
- Outlook
- Windows Server 2012
- Active Directory
- Windows Networking, Email Servers
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
- Anti-Virus Apps
- Ransomware
- The Email Laundry
- Email Servers
- Cybersecurity
- Microsoft Access, *malware
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month6 days, 20 hours left to enroll
622 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.