Move blobs to other server when the ldap is down/corrupted: Difference between revisions
m (→Purpose) |
|||
Line 30: | Line 30: | ||
{{Article Footer|Zimbra Collaboration 8.6, 8.5, 8.0|04/18/2015}} | {{Article Footer|Zimbra Collaboration 8.6, 8.5, 8.0|04/18/2015}} | ||
{{NeedSME|SME1|SME2| | {{NeedSME|SME1|SME2|Jenny Jarrard}} |
Revision as of 15:18, 21 May 2015
Article Information |
---|
This article applies to the following ZCS versions. |
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.