Hierarchical Storage Management (HSM) allows you to configure storage volumes for older messages. You can initiate an HSM session manually and you can schedule to run the HSM session through the crontab. HSM sessions should be scheduled to run on a regular basis. Messages are moved to the secondary storage volume based on the HSM policy.
The HSM policy is configured either from the Global Settings>HSM tab or from the Servers>Volumes tab. The default global HSM policy is to move messages and briefcase files more than 30 days old to the secondary volume.
The first time you run the HSM session, you should schedule the session to run in off-peak hours. When you start the HSM session, the process iterates through the mailboxes on the server, moving messages that meet the threshold age limit. Depending on how many messages will be moved, the session could take some time.
Go to Configure>Server.
Select the server and in the gear icon, click Edit.
When the server pages open, in the gear icon, click HSM.
In the dialog box, click Start HSM Session.
Click OK. The session continues to run.
While the session is running, a progress bar on the HSM dialog shows how many mailboxes have been processed and how man, BLOBS have been moved. You can open the HSM dialog to see the current status of the session.
A HSM session can be aborted from the HSM dialog, at any time. Clicking Abort stops the session. If all the messages in a mailbox being processed were not moved before you clicked Abort, no messages from that mailbox are moved from the primary volume. Messages for mailboxes that have completed the move to the secondary volume are not moved back to the primary volume.
HSM sessions started by a cron job can be monitored and aborted from the HSM dialog.
-------------------------------------------------------------------------------------------------------
Copyright @ 2005-2017 Synacor, Inc. All rights reserved. "Zimbra" is a registered trademark of Synacor, Inc.