On a server's Volume page you manage storage volumes on the Zimbra Mailbox server. When Zimbra Collaboration Server is installed, one index volume and one message volume are configured on each mailbox server.
The Index volume is /opt/zimbra/index
The Message volume is /opt/zimbra/store
You can add new volumes, set the volume type, and set the compression threshold
Each Zimbra mailbox server is configured with one current index volume. Each mailbox is assigned to a permanent directory on the current index volume. When an account is created, the current index volume is automatically defined for the account. You cannot change which index volume the account is assigned.
As volumes become full, you can create a new current index volume for new accounts. You can add new volumes, set the volume type, and set the compression threshold.
Index volumes not marked current are still actively in use for the accounts assigned to them. Any index volume that is referenced by a mailbox as its index volume cannot be deleted.
When a new message is delivered or created, the message is saved in the current message volume. Message volumes can be created, but only one is configured as the current volume where new messages are stored. When the volume is full, you can configure a new current message volume. The current message volume receives all new messages. New messages are never stored in the previous volume.
A current volume cannot be deleted, and message volumes that have messages referencing the volume cannot be deleted.
The Volumes page shows the following information
Manage Volumes section
Volume Name. The name of the volume. The initial volumes are named index1 and message1.
Volume Root Path. The location in the file system where volume data is stored.
Volume Type. The volume type is either Index or Primary Message, Secondary Message.
Compress Blobs. When this box is checked, message blobs whose size is above the compression threshold are compressed. If blob compression is turned on, the disk space used is decreased. Note: Turning on blob compression also increases memory requirements for the server.
Compression Threshold. Messages larger than the threshold are compressed. The default threshold is 4096 bytes.
Current. A check mark is displayed next to volumes that are current.
Assign Current Volumes. This can be either the message volume, secondary message volume, or the index volume.
Assign Current Volumes section
Current primary message volume. The current primary volume name. New messages are saved in this current message volume.
Current secondary message volume. The current secondary message volume name. Older data is stored on the secondary message volume.
Current index volume. The current index volume name. As volumes become full, you can create a new current index volume for new accounts
HSM Policy section
To manage your disk utilization, you can implement a global HSM policy or a different HSM policy for each mailbox server.
Types of items to move. You can select messages, tasks, appointments, contacts,and briefcase items to move from a primary volume to the current secondary volume.
Move items older than. The default global HSM policy is to move messages and files more than 30 days old to the secondary volume. The age of items to be moved can be specified by number of days, months, weeks, hours, or minutes.
Policy String. You can use the search query language to set up other HSM policies. For example, if you wanted all messages marked as junk to be included in messages moved to the current secondary volume, you would add the following to the policy: message:in:junk before:-[x] days.
-------------------------------------------------------------------------------------------------------
Copyright @ 2005-2017 Synacor, Inc. All rights reserved. "Zimbra" is a registered trademark of Synacor, Inc.