cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange user over archived

tim_d_jordan
Level 4

I have a user that has been archived beyond what it set in the archiving policy.

The exchange policy is set to 'Based on age and quota'

The age is set to older than 6 months

The quota is set to item until mailbox reaches 80% available storage.

 

The user has a 2GB quota set on the mailbox database and he has used 500mb or space

 

The newest message that has been archived is 22nd March 2012.

The user is not aware of how to manually put items in the archive himself so I do not think that is the issue.

 

Anyone seen this before?

This is v9.03

 

Thanks

 

Tim

1 ACCEPTED SOLUTION

Accepted Solutions

Tremaine
Level 6
Employee Certified

Something similar has potentially been seen before on V8 whereby too much was archived using an 'Age and Quota' policy if there was no actual Quota set on the the mailbox.

Based on what you are saying it would appear that there may be a number of failures here, foremost for the Quota, secondly potentially ignoring the cutoff age of items if defined - Can you confirm what the setting of 'Never archive items younger than XX' is? If that is not set then set it to 3months perhaps to ensure that not too much is archived.

If you could run a report mode run against the user it would be good to see what it expects to process. Perhaps then a 2nd normal archiving run with a dtrace so you can see whether it finds a quota set for the mailbox and what policy it thinks it is supposed to be using and then another report again after the run to see what it actually did.

You may need to consider opening a support case here if you see some really obviously incorrect behaviour from a dtrace.

View solution in original post

3 REPLIES 3

Tremaine
Level 6
Employee Certified

Something similar has potentially been seen before on V8 whereby too much was archived using an 'Age and Quota' policy if there was no actual Quota set on the the mailbox.

Based on what you are saying it would appear that there may be a number of failures here, foremost for the Quota, secondly potentially ignoring the cutoff age of items if defined - Can you confirm what the setting of 'Never archive items younger than XX' is? If that is not set then set it to 3months perhaps to ensure that not too much is archived.

If you could run a report mode run against the user it would be good to see what it expects to process. Perhaps then a 2nd normal archiving run with a dtrace so you can see whether it finds a quota set for the mailbox and what policy it thinks it is supposed to be using and then another report again after the run to see what it actually did.

You may need to consider opening a support case here if you see some really obviously incorrect behaviour from a dtrace.

tim_d_jordan
Level 4

OK have decided that as the problem has started with the quota and the user does not have a specific quota just the store, that we would be best to avoid the functionality as it does not really do what we wanted to do according to the documentation anyway.

We wanted to concentrate on the users closest to their quota limit first.

Thanks

Tim

Tremaine
Level 6
Employee Certified

Even if the quota is set at the Store and the user is inheriting it EV will normally pick this up and apply it as well. Hence why it would be necessary to confirm from a dtrace or Report mode run whether this is truly the case. If not then perhaps setting one manually. Either way that would indicate a problem that would require further investigation.