Move blobs to other server when the ldap is down/corrupted

Revision as of 10:45, 12 July 2015 by Jorge de la Cruz (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Move blobs to other server when the ldap is down/corrupted

   KB 21815        Last updated on 2015-07-12  




0.00
(0 votes)

Purpose

Move blobs from one Zimbra server to another where mailbox IDs of accounts are different on both the servers.

Sometimes people just want their messages from an old/corrupted Zimbra mailbox, and here is the way we can do this. (In this scenario LDAP of the old box is not working but mysql is up. )

Resolution

Get the account address with their Mailbox ID.

mysql -e "select comment,id from zimbra.mailbox;"

Find the blobs in /opt/zimbra/store/0/{mailboxID} directory

Example 1

mysql
-----
| user@domain.coom | 2231 |

User BLOB Path
---------------
/opt/zimbra/store/0/2231/msg/0

Copy the blobs to a tmp directory on the new machine, and add the blobs to the account on the new machine.

zmmailbox -z- -m user@domain.com addMessage /Inbox 310-100.msg
zmmailbox -z- -m user@domain.com addMessage /Inbox 320-200.msg

Additional Content


Verified Against: Zimbra Collaboration 8.6, 8.5, 8.0 Date Created: 04/18/2015
Article ID: https://wiki.zimbra.com/index.php?title=Move_blobs_to_other_server_when_the_ldap_is_down/corrupted Date Modified: 2015-07-12



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 »


Wiki/KB reviewed by SME1 SME2 Jenny Jarrard Last edit by Jorge de la Cruz
Jump to: navigation, search