Setting an archive size limit is something that has been in Enterprise Vault for many versions now, but do people use it? In days gone by (okay only 6-ish years ago) when I supporting production Microsoft Exchange servers they ALWAYS had mailbox size limits in place. Not specifically to ‘cripple’ users ability to manage their emails, but more specifically to stop a few different things:
* Spinning messages – with the variety of versions of Exchange and other messaging systems at the time it wasn’t unheard of to get a message spinning out of control, bloating the size of a mailbox, and if unrestricted it would eventually consume all the disk space on the drive that the information store lived on.
* Silly users – this is the special group of people who would send 30 Mb+ email attachments to other people… multiple times a day. It’s the special group of people who would try to send a 600 Mb PST file to their secretary.
* Predicting space usage – with limited maximum sizes it was easy to manage storage.
So with Enterprise Vault being ‘my world’ for the last 6 years or so, I was pleased to learn that it was possible to set archive size limits.. but it’s one of those forgotten about aspects of Enterprise Vault, I think.
I’m a believer in setting ‘some limit’, even if it’s large… very large even. As with Microsoft Exchange it’s not completely unheard of to have the same message archived over and over and over again, causing an archive to bloat over time. (Not at quite the same crazy rate that would happen in Exchange, where a message would spin several times a second – in EV I’ve only ever seen an item be archived once per archiving run, every archiving run).
So, do you set an archive size limit? And if so, what size? If not, why not?