Defrag Exchange Mail Store
Hi, I have an Exchange 2003 server (running on Windows SBS 2003) with all
the latest service packs. It has a 48 GB Information Store.
This l weekend I dismounted it to run a defrag using eseutil. It
failed at 20% with the following error --
error -1014 JET_errOutOfBuffers Out of database page buffers
I am using this command :
Eseutil /d "d:\program files\exchsrvr\mdbdata\pri
the f drive is a NAS box with 1TB of free space.
Server is running 4 GB of ram
Attached is Page file details
Ant help on this would be great
PAGE-FILE.docx
the latest service packs. It has a 48 GB Information Store.
This l weekend I dismounted it to run a defrag using eseutil. It
failed at 20% with the following error --
error -1014 JET_errOutOfBuffers Out of database page buffers
I am using this command :
Eseutil /d "d:\program files\exchsrvr\mdbdata\pri
the f drive is a NAS box with 1TB of free space.
Server is running 4 GB of ram
Attached is Page file details
Ant help on this would be great
PAGE-FILE.docx
ASKER
No not enough space on sbs server d: drive that is why I am using NAS box for temp files
Okay - what about the Event ID 1221 question?
That only suggests you will get 2mb of disk space back by running eseutil /d, which from 48gb, seems pretty pointless.
I take it you are hoping to drastically reduce the size?
I take it you are hoping to drastically reduce the size?
ASKER
Thats was the plan, as I see from the mailbox size it is only about 20GB within exchage
Well - if you complete eseutil /d, that is all you will gain.
If you reduce the mail store retention you should (after the next online maintenance session), see much more 'white space' available to be recovered.
http://www.msexchange.org/tutorials/mf022.html
If you reduce the mail store retention you should (after the next online maintenance session), see much more 'white space' available to be recovered.
http://www.msexchange.org/tutorials/mf022.html
ASKER
can you send me on that link again, you send me something about deleted item ?
That is the correct link.
Change the mailstore retention period for mailboxes and items and that will allow you to recover more space and it means people can't recover mail emptied from their recycle bin.
Change the mailstore retention period for mailboxes and items and that will allow you to recover more space and it means people can't recover mail emptied from their recycle bin.
ASKER
ok, will try this, but what about my orginal question ?
Might be down to the NAS. Do you have any other servers on your LAN?
ASKER
None, only sbs server. small company. nas box has been working fine, storing data on it.
Never tried eseutil with a NAS box. Do you have a USB drive you can try? It will be slower though not sure if it will be supported unless the drive is USB 2.0 and formatted as NTFS.
I
Sorry my iPhone crashed.
I wouldn't attemp a eseutil /d to a database on a nas box, ideally this needs to be direct attached storage.
I wouldn't attemp a eseutil /d to a database on a nas box, ideally this needs to be direct attached storage.
Yes as you know., you can do that by copying the bin folder (actually 5 files are enough) to NAS . Then you have to defrage and copy back the defraged DB to original location and then you have to run ISINTEG on the server.
Its suggestable to have a extra copy of DB before doing this.
Its suggestable to have a extra copy of DB before doing this.
ASKER
The NAS box is connected direclty to the server using a usb connection.
The database is on the server and I am redirecting the temp file to the nas box
NAS box is http://www.lacie.com/products/product.htm?id=10477
The database is on the server and I am redirecting the temp file to the nas box
NAS box is http://www.lacie.com/products/product.htm?id=10477
Correct me if this is not you are looking for...
ASKER
Never ran ISINTEG before, what are the commands to to this ? thanks
You have to run
Isinteg -s ServerName -Fix -Test Alltests.
Incase if you find any errors you have to run again.
Also you can run this upto u see 0 errors.
Isinteg -s ServerName -Fix -Test Alltests.
Incase if you find any errors you have to run again.
Also you can run this upto u see 0 errors.
There is no need to run isinteg unless you run eseutil /p and there is no indication that this is necessary here.
Yes as said by Alanhardisty its not required, But this searches for integrity weaknesses and will fix them.
Its not at all a useless step Afaik..
Its not at all a useless step Afaik..
The question is about defragging a database not fixing corruption or integrity checking the database.
Run it if you wish but it isn't necessary.
Run it if you wish but it isn't necessary.
If you ask Microsoft I would suspect they will say this kind of USB disk is not supported in exchange 2003 this might be why eseutil is failing. You really need to try this on direct attached storage before you can suspect a partially corrupt database.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all your help, I got the defrag to run, after I stopped alot ot services from running, ie Symantec AV
The database defrag finished with no errors but the only problem is that there was very little defraged.
edb file is 48 GB and stm is 30 GB, event 1221 only gives me 40mb to free up, when I check exchange the mailboxes only add up to about 20 GB, how do I get this down, I have reducing the retention period to 5 for mailboxes.
Need help on this as the exchange keeps falling out as it is sbs2003 and limit of 75GB on mailstore.
The database defrag finished with no errors but the only problem is that there was very little defraged.
edb file is 48 GB and stm is 30 GB, event 1221 only gives me 40mb to free up, when I check exchange the mailboxes only add up to about 20 GB, how do I get this down, I have reducing the retention period to 5 for mailboxes.
Need help on this as the exchange keeps falling out as it is sbs2003 and limit of 75GB on mailstore.
I have already answered your latest question.
Please review my earlier comments relating to the retention period.
Once retention is reduced (ideally to 0), then you will be able to recover the max from the database.
If you have done this and waited 24 hours and still not much is shown in event id 1221, then people need to start deleting mail en mass, or archiving it out of the Exchange mailbox to archive.pst files locally on their PC's then you can wait for 24 hours more and see what event id 1221 shows can be reclaimed.
Please review my earlier comments relating to the retention period.
Once retention is reduced (ideally to 0), then you will be able to recover the max from the database.
If you have done this and waited 24 hours and still not much is shown in event id 1221, then people need to start deleting mail en mass, or archiving it out of the Exchange mailbox to archive.pst files locally on their PC's then you can wait for 24 hours more and see what event id 1221 shows can be reclaimed.
Do you not have much space left on the SBS server to cater for the temp file? 53gb aprox needed.