Re: Kerio connect storage issue [message #148861 is a reply to message #148852] |
Fri, 16 October 2020 17:17  |
chrwei
Messages: 186 Registered: October 2009
|
|
|
|
Outlook's archive has other issues too, like it being local on the PC and no longer redundant and backed up, and PST files being notoriously easy to corrupt if they are on a network share. I've also had issues with some email fields, attachments, and encodings being preserved when moving things between different storage formats (specifically exchange to pst, pst to kerio), though that was many years ago. For those I had to login to both servers with an IMAP client and copy them that way.
The big question is: what's your time worth vs spending money?
3rd party archiving tools is probably your best option. they exist because outlook's method is archaic and error prone. I don't have a recommendation, storage is relatively cheap, so I just keep adding more, while also encouraging people delete the cruft (multiple copies of the same attachments, marketing emails with pictures, emails you didn't really need to be CC'd on, etc).
I do use Kerio's built in archive option too, and that's placed on big cheap storage on a linux NFS server that uses zfs compression (my kerio server is also linux, but virtualized on ssd storage). it's been handy for recovering things people delete that they shouldn't have, even months later. having it on another server also keeps the CPU load of compression and searching off the production server. Not sure how that's going to work if Kerio ever switches to a database type format instead of maildir. I love maildir for this level of flexibility!
If you want something cheap and more DIY, you could even take advantage of that maildir structure and make some scripts that move things based on file date to an archive structure on USB or network share. Doing so on a live server will mess with the indexing, but a server restart should fix that. You'll also need to do file renames as you move then unless you make a new structure for each batch.
|
|
|