Turning on expiry after three years
EV904
Our paralegals have their litigation cases all entered into DA, to protect content from expiry. We finally have our go-ahead to enable expiry on our journal archive. The thing is - it's approaching 150M items. Whether I run expiry in report mode or real mode, all journal scraping stops. It acts like while expiry is processing, the system disallows any new additions.
We have had expiry running on our mailbox archive for some time, and I had it set to always run. I'm wondering if I need to trim those times down, or if the initial journal archive "figure out what can be allowed to expire" process just needs to process, and journal scraping will just have to wait.
Other than the 7085 or 7086 events that the expiry process generates, is there any other way to see if the expiry calculations are actually occuring, or what kind of progess it's making? If I utilize DTRACE, which item is worth monitoring?
As always, thank you for any insight!
Aaron
NaturesRevenge,
I've been in the same situation as you. I had a little more items to expire though :-)
I had the same experience as you did. How we 'fixed' it was more or less as follows.
Make sure the SQL server has as much RAM and Processors as possible. Do not run expiry during scheduled archiving runs. Make sure the advised SQL maintenance is being done properly, and EVERY day, whilst not expiring, nor archiving (ie during backup mode, either before or after the backup of SQL). Create a NEW Journal mailbox and a NEW journal archive, preferably in a new VSG/VS and start journaling and archiving from and to that one. Upgrade to 9.05 as advised, because that improved expiry tremendously.
If necessary, stop expiry for a day or so, to allow EV to catch up on other work. And, monitor, monitor, monitor.