View source for How to move the existing data on the secondary volume to the new storage path

{{BC|Certified}}
__FORCETOC__
<div class="col-md-12 ibox-content">
=How to move the existing data on the secondary volume to the new storage path=
{{KB|{{ZC}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}|}}
{{WIP}}
==Purpose==
How to move the existing data on the secondary volume to the new storage path.

==Resolution==
Follow the next steps:
* Create the secondary path
 mkdir /opt/zimbra/secondary
* Assign it the proper permissions
 chown zimbra:zimbra
* Mount new partition to '''/opt/zimbra/secondary''' - confirm permissions in directory and zimbra read/write
* Rsync data from '''/other/secondary /opt/zimbra/secondary'''
* Schedule a short downtime window .
* Shutdown ZCS - confirm zimbra crontab won't be kicking off a job during downtime
window
* Do a final rsync

* Move the data between the secondary and the old one:
 mv /other/secondary /other/secondary-old
* Decide to either modify the zmvolume directory path for message2 volume to be '''/opt/zimbra/secondary''', or remount and update /etc/fstab to have the 'new' partition
that was mounted at /opt/zimbra/secondary to now be /other/secondary
* Start zimbra, confirm HSM works and no missing blob messages happen.

If you don't want any downtime, you could try using zmsoap 's MoveBlobsRequest - but there might be a bug in that approach. We have a case right now where not all the blobs moved and we're trying to thrash thru why that is.

==Additional Content==
* No related content.

{{Article Footer|Zimbra Collaboration 8.6, 8.5, 8.0|05/05/2015}}
{{NeedSME|SME1|SME2|Copyeditor}}