Messaging Server and Mailstore Best Practices - "Muling" Over Your Options
By Joesciallo-Oracle on Dec 20, 2006
When it comes to setting up the disk partitions on your mailstore, the Messaging Server experts agree: spread your mailboxes out across multiple partitions. The benefits include:
- Faster times to back up and restore mailboxes
- Less risk of data loss (you lose only those mailboxes on a particular partition instead of all mailboxes on a single partition)
- Increased performance and scalability (assuming the partitions are accessing separate spindles)
- The ability to run many imsbackup instances in parallel, one per partition, which can help to back up many gigabytes of mail in the 6-8 hours you normally have
Deciding on The Number of PartitionsTo decide upon the number of partitions to create, consider the following:
- Partitions are logical objects, so equate the partition to a file system. Because of this, your partitions depend on the file system type.
- With UFS you have a limited set of inodes to manage. Pay attention to the expected mailbox population (number of mails, attachments, minimum and maximum size, and so on) to estimate the number of inodes needed. Based on that, define your file systems/partitions.
In the Solaris OS environment, use the
df -o icommand to see the inodes your file systems have.
- As a best practice, limit a single partition's size to less than 1 TByte. It is further suggested that you use no more than 900 GB per partition.
Quick Primer on Configuring Mailstore PartitionsTo configure a mailstore partition, you make the mailstore aware of the partitions by using the
configutilcommand, for example:
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.
Next, on the user directory entry, set the
mailmessagestore attribute to the nickname of the partition.
Additionally, you can set the default partition (if the user doesn't have a
mailmessagestore attribute) by using the
configutil store.defaultpartition attribute as well as the default primary partition with the following command:
configutil -o store.partition.primary.path -v path