Move blobs to other server when the ldap is down/corrupted: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
{{ | {{BC|Certified}} | ||
__FORCETOC__ | |||
<div class="col-md-12 ibox-content"> | |||
=Move blobs to other server when the ldap is down/corrupted= | =Move blobs to other server when the ldap is down/corrupted= | ||
{{KB|{{ZC}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}}} | |||
{{WIP}} | |||
==Purpose== | ==Purpose== | ||
Move blobs from one Zimbra server to another where mailbox IDs of accounts are different on both the servers. | Move blobs from one Zimbra server to another where mailbox IDs of accounts are different on both the servers. |
Latest revision as of 10:45, 12 July 2015
Move blobs to other server when the ldap is down/corrupted
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
- You can find more information in the next Wiki article.