Difference between revisions of "ZCS88-zxbackup-Loss-of-HSM-Volume"

Line 48: Line 48:
  
 
zxsuite hsm doupdatevolume hsm current_volume true
 
zxsuite hsm doupdatevolume hsm current_volume true
 +
</pre></code>
 +
 +
If you see this error...
 +
<code><pre>
 +
Error creating volume: com.zimbra.cs.volume.VolumeServiceException: volume with the same id, name, or path already exists
 +
</pre></code>
 +
 +
You will need to remove the old volume ID from mysql first.
 +
<code><pre>
 +
mysql zimbra -e "delete from current_volumes where secondary_message_volume_id='3';"
 +
 +
mysql zimbra -e "delete from volume where id='3';"
 +
</pre></code>
 +
 +
===Check for Missing BLOBS===
 +
<code><pre>
 +
zxsuite hsm doCheckBlobs start
 
</pre></code>
 
</pre></code>

Revision as of 17:03, 5 September 2017

ZCS 8.8 Article ZCS 8.8


Loss of HSM Volume

Display List of Volumes

zxsuite hsm getallvolumes

If there is an HSM volume at /opt/zimbra/hsm, the listing would look something like this...

        primaries                               

                id                                                          1
                name                                                        message1
                path                                                        /opt/zimbra/store
                compressed                                                  false
                threshold                                                   4096
                storeType                                                   LOCAL
                isCurrent                                                   true
                volumeType                                                  primary
        secondaries                             

                id                                                          3
                name                                                        hsm
                path                                                        /opt/zimbra/hsm
                compressed                                                  false
                threshold                                                   4096
                storeType                                                   LOCAL
                isCurrent                                                   true
                volumeType                                                  secondary
        indexes                                 

                id                                                          2
                name                                                        index1
                path                                                        /opt/zimbra/index
                compressed                                                  false
                threshold                                                   4096
                storeType                                                   LOCAL
                isCurrent                                                   true
                volumeType                                                  index

If the /opt/zimbra/hsm volume went missing, you can create the volume with this command

zxsuite hsm docreatevolume secondary "hsm" "/opt/zimbra/hsm/" false 4096

zxsuite hsm doupdatevolume hsm current_volume true

If you see this error...

Error creating volume: com.zimbra.cs.volume.VolumeServiceException: volume with the same id, name, or path already exists

You will need to remove the old volume ID from mysql first.

mysql zimbra -e "delete from current_volumes where secondary_message_volume_id='3';"

mysql zimbra -e "delete from volume where id='3';"

Check for Missing BLOBS

zxsuite hsm doCheckBlobs start
Jump to: navigation, search