| Mail Server Storage Management [message #140329] |
Tue, 03 July 2018 23:02  |
ShaneLG
Messages: 15
Registered: October 2017
Location: California
|
|
|
|
Hello,
Our mail server is getting pretty full, it's at about 91% capacity. What are the best practices as far as storage management goes? I want to implement a policy to delete user's emails over "x" amount of years. I know this can be accomplished through Kerio Admin interface. Just curious to see what everyone else is doing?
Is there anyway to enforce a policy to delete user's emails over "x" amount of years but exclude a few users? The problem for me is my CEO wants to keep all of his emails from forever ago.. What would be the best way to delete everyone's older emails but not touching his emails? Could I just have him store them onto a .PST file and just store that file somewhere else?
Any input would be appreciated, just want to bounce ideas off people who have tried to do the same thing.
|
|
|
|
| Re: Mail Server Storage Management [message #140330 is a reply to message #140329] |
Wed, 04 July 2018 01:33  |
zebby
Messages: 154
Registered: March 2009
|
|
|
|
Hi
You can set a domain wide policy to delete items after x number of days but also then override this at user level if you have, let's be honest, (usually) senior managers who must have that email from 15 years ago. From someone who doesn't work for that company anymore. Who then retired. Who then died. But if they do reach out from the grave they will still have the original email thread.
We use MailStore to archive users mail then delete everything from Kerio after 1 year.
We keep mail in MailStore for 5 years, possibly over kill but our insurance comapny is happy with this as contracts get transferred using email.
All of our users are on Outlook so this keeps Outlook pretty trim. Searching mail in Outlook with Kerio is, even with just one year of mail, above and beyond piss poor where as in MailStore it is blisteringly quick.
|
|
|
|
| Re: Mail Server Storage Management [message #140332 is a reply to message #140330] |
Wed, 04 July 2018 01:48 |
ShaneLG
Messages: 15
Registered: October 2017
Location: California
|
|
|
|
I will have to look into MailStore, sounds like something we could benefit from.
Question: You said I could set a Domain wide policy and override it at a user level.. How would I go about overriding it at a user level? I know how to set Domain policy for messages just unsure how you override that on a per user basis? Could you elaborate?
|
|
|
|
|
|
| Re: Mail Server Storage Management [message #140347 is a reply to message #140341] |
Thu, 05 July 2018 12:28 |
Maerad
Messages: 275
Registered: August 2013
|
|
|
|
Honestly - in todays age storage is cheap as fuck, so just tell your CEO that the space runs low and you need to upgrade the storage. Not bad to change the disks from time to time anyway. If he declines, tell him about the autodelete etc.
Btw. about the automatic delete - don't keep this at an IT level - this is also a big organization change and you will need every Department with you in this. Check your workflow with them. Do you archive all important mails in a separate program like an ERP System? If not, can you? This way only the important stuff would be kept and you can safely enable a delete rule. Then you can select a group of ppl without deleting rules.
For legal reasons, I would enable the Kerio Archive function and save all mails with it, at least for the archiving time given by law (10 years in germany).
This way you can rebuild in a worst case scenario. And this archive can be saved on another harddrive/disk/whatever.
|
|
|
|
|
|
| Re: Mail Server Storage Management [message #140352 is a reply to message #140348] |
Thu, 05 July 2018 14:02 |
Maerad
Messages: 275
Registered: August 2013
|
|
|
|
zebby wrote on Thu, 05 July 2018 13:21Maerad wrote on Thu, 05 July 2018 11:28Honestly - in todays age storage is cheap as fuck
True, but Kerio + Outlook + large mailboxes = as slow as fuck.
Depends on the hardware I guess. We use a terminal server and I configured (even made a how to thread here) it in a way, that the KOFF Cache per User is created on a single SSD in the server with enough space for the mailboxes. It's fast as hell even with 35 users. Had it on the TS Raid 10 (with 6 SAS HDD) too and the performance was ok, but the search took a bit longer.
Even with a local PC (got 40k mails in my box) and a usual SATA 7200 rpm I had no real problems with it. Even our remote workers with laptops and the usual 5k rpm disks have no problem with it. Guess it's important that you config KOFF in a way, that it wont cache every mail but only the past year or two. Usually you wont need more and the index is for all mails - they are just saved remotely.
Maybe the Kerio Client itself makes more I/O load on the server, but below 100 users you might be ok with a simple raid 10 and SAS. For more I would use SSD or even M.2. Well, not the server SSD, those are way more expensive and last not much longer. Admin friend of mine tried 850 Pro vs. Samsungs PM863a or SM863a Server HDD. Both used in 2 different raid arrays with the same I/O. They check them once per year (since 2015 I believe) how the wear is and both had no problems so far. So IMHO with a raid you can easily use any "Pro" SSD and don't really need a server SSD IF you are on a budget at least.
|
|
|
|
Members
Search
Help
Register
Login
Home
