| Author |
Message |
Martin Smulian
Guest
|
 Posted:
Mon Nov 21, 2005 5:58 pm Post subject:
MDB Size Problem |
|
|
Looking at the database size from Ssytem Manger, shows a size of approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
|
|
| Back to top |
|
 |
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Mon Nov 21, 2005 5:58 pm Post subject:
Re: MDB Size Problem |
|
|
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
| Quote: |
Looking at the database size from Ssytem Manger, shows a size of approx
14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
|
Perhaps nothing. Before running ESEUTIL, always best to look in your
application event logs for 1221 events - online maintenance will tell you
how much disk space you can recover - sometimes, often, it's just not worth
it. When you say you're looking at the database size from system manager,
what do you mean, exactly - adding up mailbox sizes? Remember, there are
other things that take up space too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run eseutil -
and don't run it if you can't recover more than a pittance. It is not meant
to be run as a part of your regular administrative tasks. Just keep an eye
on things and make sure you're using mailbox quotas that ensure you won't go
over your limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
| Quote: |
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user |
|
|
| Back to top |
|
|
Martin Smulian
Guest
|
| Posted:
Tue Nov 22, 2005 9:58 am Post subject:
Re: MDB Size Problem |
|
|
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each subsequent run this
drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between 1:45 am and
4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance Interval is
Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours From
Midnight" is at the default 5, but there is no corresponding 1221 entry (which I
would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
Thanks,
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
| Quote: |
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of approx
14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in your
application event logs for 1221 events - online maintenance will tell you
how much disk space you can recover - sometimes, often, it's just not worth
it. When you say you're looking at the database size from system manager,
what do you mean, exactly - adding up mailbox sizes? Remember, there are
other things that take up space too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run eseutil -
and don't run it if you can't recover more than a pittance. It is not meant
to be run as a part of your regular administrative tasks. Just keep an eye
on things and make sure you're using mailbox quotas that ensure you won't go
over your limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
|
Martin
Just another confused user
|
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Tue Nov 22, 2005 10:09 pm Post subject:
Re: MDB Size Problem |
|
|
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
| Quote: | I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
|
I don't think you do stop it. I'm not sure what you're looking at, but you
should trust the final 1221 message per store. May I ask why you're worrying
about this?
| Quote: |
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in your
application event logs for 1221 events - online maintenance will
tell you how much disk space you can recover - sometimes, often,
it's just not worth it. When you say you're looking at the database
size from system manager, what do you mean, exactly - adding up
mailbox sizes? Remember, there are other things that take up space
too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user |
|
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Wed Nov 23, 2005 5:58 pm Post subject:
Re: MDB Size Problem |
|
|
In news:elGho5C8FHA.476@TK2MSFTNGP15.phx.gbl,
PaulS <please_reply@thepost.com> typed:
| Quote: | "Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
message news:O3vJIG97FHA.3760@TK2MSFTNGP14.phx.gbl...
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
I don't think you do stop it. I'm not sure what you're looking at,
but you should trust the final 1221 message per store. May I ask why
you're worrying about this?
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in
your application event logs for 1221 events - online maintenance
will tell you how much disk space you can recover - sometimes,
often, it's just not worth it. When you say you're looking at the
database size from system manager, what do you mean, exactly -
adding up mailbox sizes? Remember, there are other things that
take up space too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user
Is Exchange SP2 out already for SBS2003?
|
SBS2003 includes Exchange 2003 Standard, so yes. The fact that it's SBS
makes no difference.
(make sure you uninstall the IMF in add/remove programs before installing
this) |
|
| Back to top |
|
|
PaulS
Guest
|
| Posted:
Wed Nov 23, 2005 5:58 pm Post subject:
Re: MDB Size Problem |
|
|
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:O3vJIG97FHA.3760@TK2MSFTNGP14.phx.gbl...
| Quote: |
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
I don't think you do stop it. I'm not sure what you're looking at, but you
should trust the final 1221 message per store. May I ask why you're
worrying about this?
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in your
application event logs for 1221 events - online maintenance will
tell you how much disk space you can recover - sometimes, often,
it's just not worth it. When you say you're looking at the database
size from system manager, what do you mean, exactly - adding up
mailbox sizes? Remember, there are other things that take up space
too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user
|
Is Exchange SP2 out already for SBS2003? |
|
| Back to top |
|
|
Martin Smulian
Guest
|
| Posted:
Thu Nov 24, 2005 5:58 pm Post subject:
Re: MDB Size Problem |
|
|
The problem arises as the first 1221 entry (the first online defrag?) shows 5Gb
recoverable, but by the last this has reduced to 210Mb. if I then run eseutil,
it is only the 210MB that gets removed.
Background
I need to load, de-duplicate, re-organise and then remove a series of archives
for a user. Adding these in will add approx 15Gb. Based on what is currently
happening, when I re-archive and remove from the store, I will only be able to
remove this 15Gb (and the current 5Gb) at a rate of 210Mb per run.
Martin
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
| Quote: |
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
I don't think you do stop it. I'm not sure what you're looking at, but you
should trust the final 1221 message per store. May I ask why you're worrying
about this?
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in your
application event logs for 1221 events - online maintenance will
tell you how much disk space you can recover - sometimes, often,
it's just not worth it. When you say you're looking at the database
size from system manager, what do you mean, exactly - adding up
mailbox sizes? Remember, there are other things that take up space
too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user
|
Martin
Just another confused user |
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Thu Nov 24, 2005 5:58 pm Post subject:
Re: MDB Size Problem |
|
|
In news:5ncbo1t0vkj4eaujgbi3nvqo06v93naosc@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
| Quote: | The problem arises as the first 1221 entry (the first online defrag?)
shows 5Gb recoverable, but by the last this has reduced to 210Mb. if
I then run eseutil, it is only the 210MB that gets removed.
|
Because that's all it found it as whitespace after online maintenance ran.
That's all there is.
| Quote: |
Background
I need to load, de-duplicate, re-organise and then remove a series of
archives for a user. Adding these in will add approx 15Gb. Based on
what is currently happening, when I re-archive and remove from the
store, I will only be able to remove this 15Gb (and the current 5Gb)
at a rate of 210Mb per run.
|
No, I don't think so. See what happens after you've removed more data.
| Quote: |
Martin
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
I don't think you do stop it. I'm not sure what you're looking at,
but you should trust the final 1221 message per store. May I ask why
you're worrying about this?
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in
your application event logs for 1221 events - online maintenance
will tell you how much disk space you can recover - sometimes,
often, it's just not worth it. When you say you're looking at the
database size from system manager, what do you mean, exactly -
adding up mailbox sizes? Remember, there are other things that
take up space too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user
Martin
Just another confused user |
|
|
| Back to top |
|
|
Martin Smulian
Guest
|
| Posted:
Mon Nov 28, 2005 5:05 pm Post subject:
Re: MDB Size Problem |
|
|
Yesterday I tried running eseutil after the first 1221 and succesfully removed
the 5Gb.
Will be adding and deleting data again today and will then re-visit this
problem.
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
| Quote: |
In news:5ncbo1t0vkj4eaujgbi3nvqo06v93naosc@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
The problem arises as the first 1221 entry (the first online defrag?)
shows 5Gb recoverable, but by the last this has reduced to 210Mb. if
I then run eseutil, it is only the 210MB that gets removed.
Because that's all it found it as whitespace after online maintenance ran.
That's all there is.
Background
I need to load, de-duplicate, re-organise and then remove a series of
archives for a user. Adding these in will add approx 15Gb. Based on
what is currently happening, when I re-archive and remove from the
store, I will only be able to remove this 15Gb (and the current 5Gb)
at a rate of 210Mb per run.
No, I don't think so. See what happens after you've removed more data.
Martin
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
In news:2cn5o15q5esj3g33ucbnevt9tosj8shh52@4ax.com,
Martin Smulian <martin@msmulian.demon.co.uk> typed:
I have looked at the 1221 events and am now even more confused.
I typically have 4 or 5 1221 events each night.
On the first run it shows approx 5Gb of free space, on each
subsequent run this drops to 218mb.
The first run finishes between 9 and 10 pm, the remainder between
1:45 am and 4:30 am
In System Manager.. Mailbox Store..Properties the Maintenance
Interval is Custom (9:00 pm to 2:00 am).
Checking the Registry the "Database Size Check Start Time in Hours
From Midnight" is at the default 5, but there is no corresponding
1221 entry (which I would expect between 5:45 and 6:00 am.
What I would like to understand
Why is the online defragmentation running more than once each night?
Why is the White space reduced for the 2nd and subsequent defrags?
How do I stop this behaviour?
I don't think you do stop it. I'm not sure what you're looking at,
but you should trust the final 1221 message per store. May I ask why
you're worrying about this?
Thanks,
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote:
"Martin Smulian" <martin@msmulian.demon.co.uk> wrote in message
news:j6h3o1hruqe6i1vrkco82on1kvvp00t9se@4ax.com...
Looking at the database size from Ssytem Manger, shows a size of
approx 14Gb.
The size on disk is approx 18Gb.
I have run Eseutil, but the size reduction was only about 0.2 Gb.
Any ideas what may be going wrong.
Perhaps nothing. Before running ESEUTIL, always best to look in
your application event logs for 1221 events - online maintenance
will tell you how much disk space you can recover - sometimes,
often, it's just not worth it. When you say you're looking at the
database size from system manager, what do you mean, exactly -
adding up mailbox sizes? Remember, there are other things that
take up space too, such as deleted item retention.
If you don't have a serious need to recover whitespace, don't run
eseutil - and don't run it if you can't recover more than a
pittance. It is not meant to be run as a part of your regular
administrative tasks. Just keep an eye on things and make sure
you're using mailbox quotas that ensure you won't go over your
limits (now 75GB in SP2 if you "unlock" it from 18GB)
http://hellomate.typepad.com/exchange/2005/11/exchange_2003_s.html
I am running SBS2003 with Exchange SP2
Thanks,
Martin
Martin
Just another confused user
Martin
Just another confused user
Martin
Just another confused user
|
Martin
Just another confused user |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in