Hi, > >Ok, as I am running with just 1 partition as well, what would I need to > >partition on a server that handles just 2-3K msg per day? > > There isn't much need to do or change anything for such a low volume, but > if you are going to re-do or a do a new machine,
I'm going to upgrade to a new machine this week, so it's either now or in 3 years. ;-) > the concept is to keep the > types of disk i/o on separate, dedicated partitions, or separate disks, or > separate controllers, in that order for these types of i/o: > > OS + apps > swap > mailqueue > webmail work space > logging > mailboxes I'm going to use just the 2 disks in a RAID 1 config, the RAID being managed by Windows itself as I have cpu cycles to spare. I have thought about partitioning however: - putting the spools files on a seperate partition will generate a lot move movement on the diskheads as they have to move from one part of the disk to another. - I might put the student mailboxes on a different partition but I probably wont be able to put the staf mailboxes somewhere else, by default they are part of the C:\Imail directory as that is the default domain. - Logging can only be separated when using something like kiwi-log as Imail simply dumps the logfiles in the spooldirectory. I have to move them manually after each day to a log archive directory. What is webmail "workspace"? Maybe I should create a C: and D: drive. Use the C: drive for: OS+apps, swap, mailqueue, webmail work space (whatever that may be) and logging, and use the D: drive for the mailboxes. But appart from the fragmentation I don't see the advantage. To me there only seems to be an advantage when using separate disks in stead of seperate partitions. Met vriendelijke groet, Bonno Bloksma --- [This E-mail scanned for viruses by Declude Virus using f-prot and Sophos] To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
