Zimbra NG Modules/Zimbra NG HSM/Zimbra Stores

Revision as of 12:07, 29 November 2017 by Jorge de la Cruz (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Zimbra NG HSM - Zimbra Stores

Zimbra NG HSM - Zimbra Stores

The Basics: types of stores and their uses

Zimbra allows for two different types of stores to be used:

  • Index Store: A store that contains informations about your data used by Apache Lucene to provide indexing and search functions.
  • Data Store: A store that contains all your Zimbra data organized in a MySql database

You can have multiple stores of each kind, but only one Index Store, one Primary Data Store and one Secondary Data Store can be set as "Current" (meaning that is currently used by Zimbra).

Primary and Secondary Data Stores

A Data Store in Zimbra can be either a Primary Data Store or a Secondary Data Store - the meaning of "primary" and "secondary" is explained here. The Primary/Secondary paradigm doesn't apply to Index Stores.

Data is moved between the "current" Primary Data Store and the "current" Secondary Data Store accordingly to a policy defined by the administrator.

Zimbra NG HSM: Moving Items between Stores

The main feature of the Zimbra NG HSM module is the ability of applying the defined policy and move items between the Primary and Secondary datastore.

The move can be triggered in three different ways:

  • Click the "Apply Policy" button in the Zimbra NG Modules Administration Zimlet
  • Start the doMoveBlobs operation through the Zimbra NG Modules CLI
  • Enable the Policy Application Scheduling in the Zimbra NG Modules Administration Zimlet and wait for it to start automatically

Once the move is started the following operations are performed:

  • Zimbra NG HSM scans through the Primary Store to see which items comply to the defined policy
  • All the Blobs of the tems found in the first step is copied to the Secondary Store
  • The database entries related to the copied items are updated to reflect the move
  • If the second and the third steps are completed successfully (and only in this case), the old Blobs are deleted from the Primary Store

The Move operation is "stateful" - each step is executed only if the previous ones have been completed successfully - so the risk of data loss during a Move operation is virtually nonexistent.

Zimbra NG Modules


Latest Version: 8.8

Zimbra NG Modules Resources

Here you can find useful resources for your Zimbra NG Modules

Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search