Since EX server version has not been described its very hard for us to comment on this scenario, assumtion is that once all the containers are closed and indexed all the related data gets cleared up from MSGCENTER subdirectories. If you see emails with old dates that could be just because you are running EmailXtract and it might have found some old emails.
Please remember that even if containers are packaged still there could be mail messages, attachments and other filed referrenced by indexer and waiting to be indexed, once indexer will finish the job it will de-reference the files in MSGCENTER. Forefully killing certain threads can also cause few files to be left at different directories because threads will be lost which were keeping eyes on the files.
Also 4.81.216 version had a code defect where MSGCENTER was not getting cleared up properly which has been addressed in the next patch kit.
You can folllow support note I have created around that time esg90075 using powerlink.emc.com , the same support note also guides you on how to clear MSGCENTER in such situation.
Rest if you like you can open a support ticket with EMC EmailXtnder Support to get the issue analyzed by the support engineer.
One more thing I forgot to mention is EmailXtaminer,
If you have EmailXaminer configured and registry key on EX server is set to 1 for EXM, then EX will keep messages on EX server till EXM reviewers review the messages.
Thanks for posting the additional information. EXM is not installed on this server, however, even after succesfully updating to 4.80 Service Pack 1 the problem still exists. There amount of .ref and .access files in the MsgCenter directory keeps growing.
This is a problem describer in the EXAdmingGuide. The guide advises to check that the indexer is indexing data. When performing these particular checks there doesn't seem to be any problem though.
What I also notice is that, sometimes in the healthcheck utility, volumes show up with a transparant folder icon. This can be resolved by right-clicking them and loading the index. So maybe there's something wrong with indexing even though the checks seem ok.
For the record, the current configuration: EmailXtender 4.81.564 - Archiving all mail per month without any filter rules EmailXtract 4.81.564 - Plays no active roll, used in the initial configuration Exchange 2003 - All mail is sent to a catchallbox which Xtender connects to
Did you clean up MSGCENTER before upgrade ? A good idea is to go from clean environment to a clean environment while upgrading. That way we know that issue occured after upgrade. Yes there could be few .REF and .ACCESS file in the subdirectories because indexer uses those and then de-reference those once the job is done.
A good idea is to clean clean MSGCENTER and then after a day or two pause journaling, close all containers and also wait for indexer to finish its jobs. If after all that still files are left you can speak to support engineer because you are able to reproduce the same and would be easy for support engineer to take it further.
RKatwal
2 Intern
•
600 Posts
0
May 25th, 2008 21:00
Since EX server version has not been described its very hard for us to comment on this scenario, assumtion is that once all the containers are closed and indexed all the related data gets cleared up from MSGCENTER subdirectories. If you see emails with old dates that could be just because you are running EmailXtract and it might have found some old emails.
Please remember that even if containers are packaged still there could be mail messages, attachments and other filed referrenced by indexer and waiting to be indexed, once indexer will finish the job it will de-reference the files in MSGCENTER. Forefully killing certain threads can also cause few files to be left at different directories because threads will be lost which were keeping eyes on the files.
Also 4.81.216 version had a code defect where MSGCENTER was not getting cleared up properly which has been addressed in the next patch kit.
You can folllow support note I have created around that time esg90075 using powerlink.emc.com , the same support note also guides you on how to clear MSGCENTER in such situation.
Rest if you like you can open a support ticket with EMC EmailXtnder Support to get the issue analyzed by the support engineer.
Hope this helps.
Regards,
Raj
RKatwal
2 Intern
•
600 Posts
1
May 26th, 2008 18:00
If you have EmailXaminer configured and registry key on EX server is set to 1 for EXM, then EX will keep messages on EX server till EXM reviewers review the messages.
RRR
4 Operator
•
5.7K Posts
0
May 27th, 2008 01:00
Welcome to the forums, Ramon !
RamonB1
6 Posts
0
May 27th, 2008 01:00
RRR
4 Operator
•
5.7K Posts
0
June 5th, 2008 02:00
RamonB1
6 Posts
0
June 5th, 2008 02:00
This is a problem describer in the EXAdmingGuide. The guide advises to check that the indexer is indexing data. When performing these particular checks there doesn't seem to be any problem though.
What I also notice is that, sometimes in the healthcheck utility, volumes show up with a transparant folder icon. This can be resolved by right-clicking them and loading the index. So maybe there's something wrong with indexing even though the checks seem ok.
For the record, the current configuration:
EmailXtender 4.81.564 - Archiving all mail per month without any filter rules
EmailXtract 4.81.564 - Plays no active roll, used in the initial configuration
Exchange 2003 - All mail is sent to a catchallbox which Xtender connects to
Message was edited by:
RamonB
RKatwal
2 Intern
•
600 Posts
0
June 5th, 2008 21:00
Did you clean up MSGCENTER before upgrade ? A good idea is to go from clean environment to a clean environment while upgrading. That way we know that issue occured after upgrade. Yes there could be few .REF and .ACCESS file in the subdirectories because indexer uses those and then de-reference those once the job is done.
A good idea is to clean clean MSGCENTER and then after a day or two pause journaling, close all containers and also wait for indexer to finish its jobs. If after all that still files are left you can speak to support engineer because you are able to reproduce the same and would be easy for support engineer to take it further.
Hope this helps.
Thanks,
Raj