ZCS Administrator Guide 8.0
ZCS Administrator Guide 8.0
Network Edition


Managing Configuration > Storage Management

Storage Management
Managing Storage Volumes
In the Volume page you manage storage volumes on the Zimbra Mailbox server. When VMware Zimbra Collaboration Server is installed, one index volume and one message volume are configured on each mailbox server. You can add new volumes, set the volume type, and set the compression threshold.
Note:
Index Volumes
Each Zimbra mailbox server is configured with one current index volume. Each mailbox is assigned to a permanent directory on the current index volume. You cannot change which 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.
Message Volumes
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.
Implementing Hierarchical Storage Management
Hierarchical Storage Management (HSM) allows you to configure storage
volumes for older messages. HSM is a process of moving older data from the primary volume to the current secondary volume based on the age of the data.
To manage your disk utilization, implement a global HSM policy or a HSM policy for each mailbox server. The policy configured on individual servers overrides the policy configured as the global policy.
Email messages and the other items in the account are moved from the primary volume to the current secondary volume based on the HSM policy. Users are not aware of any change and do not see any noticeable differences when opening older items that have been moved.
The default global HSM policy moves messages and document files more than 30 days old to the secondary volume. You can also select to move tasks, appointments, and contacts. The schedule for moving can be set for items older than a specified number of days, months, weeks, hours, minutes.
In addition to selecting different items to move, you can use the search query language to set up other HSM policies. For example:
*
*
Note:
Scheduling HSM Sessions
Sessions to move messages to the secondary volume are scheduled in your cron table. From the administration console, when you select a server, you can manually start a HSM session, monitor HSM sessions, and abort HSM sessions that are in progress from the Volumes page.
You can manually start an HSM session from the server’s gear icon menu.
When you abort a session and then restart the process, the HSM session looks for entries in the primary store that meet the HSM age criteria. Any entries that were moved in the previous run would be excluded, as they would no longer exist in the primary store.
HSM jobs can be configured to be a specific batch size. The zimbraHsmBatchSize attribute can be configured either as a global setting or per server to specify the maximum number of items to move during a single HSM operation. The default value is 10000. If the limit is exceeded the HSM operation is repeated until all qualifying items are moved.
*
zmprov mcf zimbraHsmBatchSize <num>
*
zmprov ms `hostname` zimbraHsmBatchSize <num>
Copyright © 2012 VMware Inc.