Due to both IMail and Declude logging in such a way that they can severely fragment a drive, I recommend first logging to the spool and then moving the logs daily, or even hourly if there is enough volume, to another drive.  Since IMail logs to the spool without an option to do otherwise, you might as well dump the Declude logs in there as well.  Moving them will effectively defragment the drive that they were originally on and write them to the new drive in defragmented format as well.  Naturally you would script this and run it with your scheduler.

Before the fragmentation was so bad that one day's worth of logs would fully fragment a 5 GB partition, and if I didn't catch it within a few days, it would be so fragmented that Windows wouldn't defrag the drive due to a lack of clean space despite the fact that it was over 80% free.  Seems that the problem is somewhat exponential with volume.  Since I started doing this, my spool drive as well as the entire server has been without need to be fragmented.  This also enhances performance, especially on systems that don't have a lot of I/O to spare.

Matt



Darin Cox wrote:
It depends on your volume, but you can probably spool more than the machine can handle with a 5GB partition.
 
And logging might need a bit more, depending on your volume, what level of logging you do, and your log retention/archival policy.  We do high logging (but not debug) for all processes, zip the
previous month's logs, and retain for 6 months (probably overkill).
 
We use about 6GB for the logging per 1000 email addresses (users&aliases), so I would probably allocate 8-10GB/1000, assuming monthly zipping of logs

Darin.
 
 
----- Original Message -----
Sent: Saturday, October 23, 2004 8:47 AM
Subject: RE: [Declude.JunkMail] iMail, Declude and Killer Web Mail Installation Question

15GB for spooling would be overkill, as if you had that many messages sitting in the spool, you have got a problem.

 

5GB would probably be overkill, but I would use 5GB.

 

John Tolmachoff

Engineer/Consultant/Owner

eServices For You

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Wolf Tombe
Sent:
Saturday, October 23, 2004 4:49 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] iMail, Declude and Killer Web Mail Installation Question

 

Thanks guys!  This was exactly the type of advice I was looking for.  One quick follow on question, are their any recommendations or calculations I should use for determining the amount of space to allocate for spool and logging directories as compared to main/user directory size?  Since I have roughly 130 Gb to use for iMail.  Would allocating 100Gb for user and iMail program area and 15 Gb each for logging and spooling be reasonable, not-enough or overkill?

 

Wolf

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark E. Smith
Sent:
Friday, October 22, 2004 2:02 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] iMail, Declude and Killer Web Mail Installation Question

 

Adding to this, I use the mounted volume feature (added in W2000 and to Unix on day 1)  so that the filesystem seems seamless to Imail/Declude/Sniffer, etc.

For example, I have the following volumes:

 

C:\     System

e:\     Imail

F:\    Imail Spool --- Mounted to e:\imail\spool

g:\    Declude Junkmail/virus Log Files -- Mounted to e:\imail\DecludeLogs

h:\    SpamChk Logs    -- Mounted to e:\imail\spamchk\spamchklogs

 

Config files just use e:\imail\blah blah to reference everything.

That way if I want to change something or just revert to a single filesystem I don't need to change config files.

 

It's probably not necessary but this helps cut down on NTFS corruption and DR times by putting everything on its own filesystem.

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darin Cox
Sent:
Friday, October 22, 2004 12:16 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] iMail, Declude and Killer Web Mail Installation Question

Separate, most definitely.  OS should always be separate from other services, and each service should be in it's own partition, sometimes even it's own drive.

 

I would do 8GB for the OS (you can get away with less, but it depends on how much other software will be loaded), and have two or three IMail partitions.

 

One IMail partition for the main install, and a separate partition (preferably separate drives, but if you're setting up RAID you've already gone a different route) each for spool and logging.  As to size of each partition, it depends on your expected volume, but generally smaller spool partitions are better as long as they are adequate to the volume.

 

By putting spool, logging, and main installation on separate drives, you get better performance due to dedicated channels for each type of traffic, and also make it easier to defragment each partition.


Darin.

 

 

----- Original Message -----

From: Wolf Tombe

Sent: Friday, October 22, 2004 12:01 PM

Subject: [Declude.JunkMail] iMail, Declude and Killer Web Mail Installation Question

 

I’m getting ready to setup a new mail server.  I’ve purchased a Dell PowerEdge server with RAID 1 and two 148Gb drives and will be using Windows 2003 Enterprise edition as the OS.  My question has to do with partitioning the drives.  Does anyone have a recommendation as to whether I should create a small (say 4 to 8 Gb) partition just for the OS and then a larger separate partition for iMail, declude and KWM?  Or should I just create one large partition for everything?

 

I’d like to install this system to the highest standards I can right out the gate.  Since this list is one of the best sources for good solid professional advice, I’d really appreciate any guidance or opinions anyone would be willing to share.

 

Thanks!


-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================


Reply via email to