Mailboxes are stored in message store partitions, an area on a disk partition specifically devoted to storing the message store. Message store partitions are not the same as disk partitions, though for ease of maintenance, it is recommended that you have one disk partition and one file system for each message store partition. Message store partitions are directories specifically designated as a message store.
User mailboxes are stored by default in the store_root/partition/ directory (see 20.2 Message Store Directory Layout). The partition directory is a logical directory that might contain a single partition or multiple partitions. At start-up time, the partition directory contains one subpartition called the primary partition.
You can add partitions to the partition directory as necessary. For example, you might want to partition a single disk to organize your users as follows:
store_root/partition/mkting/ store_root/partition/eng/ store_root/partition/sales/
As disk storage requirements increase, you might want to map these partitions to different physical disk drives.
You should limit the number of mailboxes on any one disk. Distributing mailboxes across disks improves message delivery time (although it does not necessarily change the SMTP accept rate). The number of mailboxes you allocate per disk depends on the disk capacity and the amount of disk space allocated to each user. For example, you can allocate more mailboxes per disk if you allocate less disk space per user.
If your message store requires multiple disks, you can use RAID (Redundant Array of Inexpensive Disks) technology to ease management of multiple disks. With RAID technology, you can spread data across a series of disks but the disks appear as one logical volume so disk management is simplified. You might also want to use RAID technology for redundancy purposes; that is, to duplicate the store for failure recovery purposes.
To improve disk access, the message store and the message queue should reside on separate disks.
The partition nickname allows you to map users to a logical partition name regardless of the physical path. When setting up user accounts and specifying the message store for a user, you can use the partition nickname. The name you enter must be an alphanumeric name and must use lowercase letters.
To create and manage the partition, the user ID used to run the server must have permission to write to the location specified in the physical path.
After adding a partition, you must stop then restart the server to refresh the configuration information.
Command Line, To add a partition to the store at the command line:
configutil -o store.partition.nickname.path -v path
where nickname is the logical name of the partition and path indicates the absolute path name where the partition is stored.
To specify the path of the default primary partition:
configutil -o store.partition.primary.path -v path
By default, mailboxes are created in the primary partition. If the partition gets full, additional messages cannot be stored. There are several ways to address the problem:
Reduce the size of user mailboxes
If you are using volume management software, add additional disks
Create additional partitions (20.10.1 To Add a Partition) and move mailboxes to the new partitions
If possible, we recommend adding additional disk space to a system using volume management software since this procedure is the most transparent for the user. However, you may also move mailboxes to a different partition.
The user does not have to be disconnected from their mailbox during this migration process.
mboxutil -r should lock everything that needs to be locked. Delivery may be stalled while that happens, and POP and IMAP and therefore webmail clients, may experience a delay, but there should be no problem.
Move the user mailbox with the following command:
mboxutil -r user/<userid>/INBOX user/<userid>/INBOX <partition_name>
mboxutil -r user/ofanning/INBOX user/ofanning/INBOX secondary
Set the mailMessageStore attribute in the moved user’s LDAP entry to the name of the new partition.
Example: mailMessageStore: secondary
Inform the user that message store connection is now allowed. If applicable, change the mailAllowedServiceAccess attribute to allow POP, IMAP and HTTP services.
The default partition is the partition used when a user is created and the mailMessageStore LDAP attribute is not specified in the user entry. The mailMessageStore LDAP attribute, which specifies a user’s message store partition, should be specified in all user entries so that a default partition is not necessary. In addition, the default partition should not be changed for load balancing or any other reason. It is invalid and dangerous to change the default partition while there are still users depending on the default partition definition.
If it is absolutely necessary to change the default partition, make sure that all users on the old default partition (the one being left behind) have their mailMessageStore attribute set to their current partition (which will no longer be the default), before changing the definition of default with the configutil parameter store.defaultpartition.