- May 19, 2011
- 18,616
- 11,331
- 136
Considering that I've been waiting for an Outlook PST file (9GB in size) to finish compacting for more than three hours now (judging by process disk activity it is still working on it), I'm a bit surprised that Outlook is considered to be a reasonable choice in the workplace. Admittedly running scanpst on that file didn't take half as long, but it seems to me like Outlook PST file problems are a real block to workflow because a) they take a long time to process and b) Outlook stores everything in one file typically so everything stops if that PST file stops working.
Does anyone have any tactics for avoiding or offsetting the problem? AutoArchive might help offset the possibility that workflow is affected (and the file currently in question is the archive file), but setting AutoArchive too aggressively might also end up in workflow problems resulting from a corrupt PST file, and running the compact/scanpst operation on a machine with a strong processor in terms of single threading as well as an SSD would help (the one I'm running it on right now has a mobile C2D and an SSD).
I suppose another possibility is to use IMAP/Exchange so that the PST file is almost completely expendable but that isn't necessarily a viable option in every workplace.
Does anyone have any tactics for avoiding or offsetting the problem? AutoArchive might help offset the possibility that workflow is affected (and the file currently in question is the archive file), but setting AutoArchive too aggressively might also end up in workflow problems resulting from a corrupt PST file, and running the compact/scanpst operation on a machine with a strong processor in terms of single threading as well as an SSD would help (the one I'm running it on right now has a mobile C2D and an SSD).
I suppose another possibility is to use IMAP/Exchange so that the PST file is almost completely expendable but that isn't necessarily a viable option in every workplace.