multiple volumes

[tiger2000]

Dear All,

User's asking to add second storage for message store in ZCS Open source
edition (5.0.9). They used the local hard drive (/opt/zimbra/store ) for
message volume in the beginning, and they're planning to add second
message volume which is from another filesystem /store2.

Can anyone advise what's the correct step to do this except adding
a second message volume from Admin Console??

another question is that after we change "current message volume"
to this /store2 filesystem. can users still access their previous messages
which were stored in /opt/zimbra/store ?

Any comment will be highly appreciated.
Rgds,
Kevin

[mmorse]

The admin console > server > volumes tab is straight forward, make sure you have permission to write to the target location - see also: CLI zmvolume - Zimbra :: Wiki
(-l and -dc arguments display your volumes)

If you're curious how to view that in the DB:
su - zimbra
mysql
select * from zimbra.volume;

Originally Posted by tiger2000

another question is that after we change "current message volume" to this /store2 filesystem. can users still access their previous messages which were stored in /opt/zimbra/store ?

Yes, just realize they're NOT moved in this process, you're only pointing at the location to store any NEW data. (See below explanation.)

Thus you shouldn't remove the old store, but alternatively if you want new store2 to hold the contents of the old store as well - just move the blobs first: Volumes : Ajcody-Notes - Zimbra :: Wiki

Promised Explanation:
Each Zimbra mailbox server is configured with one current index & message (NE can add secondary HSM volumes).

When a new message is delivered or created, the message is saved in the current message volume. Additional 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. If there are accounts with messages referencing a volume it should not be deleted until you point the volume path to wherever you've now moved the items.

Each mailbox is assigned to a permanent index 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. When a new index volume is added as current, the older index volume is no longer assigned new accounts. Index volumes not marked current are still actively in use as the index volumes for accounts assigned to them. Any index volume that is referenced by a mailbox as it's index volume cannot be deleted.

(Also a handy tidbit of info: http://www.zimbra.com/forums/adminis...e-volumes.html - first tip is good for HSM > back to store, Klug's also points out that you can essentially use the same concept of Adam's above wiki link; making it a subdirectory of the new filesystem location keeps it simple.)