Just wanted to post an update and a follow-up question.
My co-worker tracked down this wiki page: http://wiki.zimbra.com/wiki/Glenno-Notes#Consolidating_one_HSM_volume_to_another
We modified this script slightly, and it appears to do just what we need to fix the migrated accounts:
store2id=2
store3id=3
for i in /opt/zimbra/db/data/mboxgroup*;
do
x=`echo $i | sed 's/.\+\///'`;
echo "Updating $i...";
mysql $x -e "UPDATE mail_item SET volume_id=$store2id WHERE volume_id=$store3id;"
done
Thanks, Glenno!
We were doing some other checking on the fixed migrated accounts and see a number of "unexpected blob" messages when running zmblobchk. We see some of these on the non-migrated accounts also, so we are not terribly concerned. We found some info that seemed to indicate that some of these could be related to "versions" of Briefcase items. Does anyone have any other insights or cautions about these "unexpected blobs"?
Has anyone else done any Zimbra-to-Zimbra account migrations and have any words of wisdom/warning?
From: "Tim Ross" <tross@calpoly.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Tuesday, August 20, 2013 9:40:38 AM
Subject: Re: Migrating accounts and HSM volumes
Matt,
Sorry, I'd already left for the day yesterday. My fellow email admin and I are not Ruby programmers. I think we can probably whip something up with Perl from some research we did yesterday, but if that doesn't pan out, I will grab your script and give it a look.
Thanks!
From: "Matt Mencel" <MR-Mencel@wiu.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Cc: tross@calpoly.edu
Sent: Monday, August 19, 2013 6:45:30 PM
Subject: Re: Migrating accounts and HSM volumes
Forgot I'd put it up on Github awhile ago for somebody else. Let me know if it helps you.
https://github.com/MattMencel/repair_disconnected_zimbra_blobs
If you don't know Ruby, you'll need to do a little work up front installing a couple Ruby Gems. The MySQL gem is the only one that might give you some trouble. If you need help getting it to work let me know. I've got some time this evening if you want to call or setup a screen share with
https://join.me/ or some other tool.
Matt
From: "Matt Mencel" <MR-Mencel@wiu.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 8:24:45 PM
Subject: Re: Migrating accounts and HSM volumes
Hi Tim,
I wrote a Ruby script to solve this exact issue in our situation. I can get it to you and you can use it as is or rewrite it in the language of your choice if you want.
I am migrating accounts from old physical hardware running RHEL5 with three volumes (store, hsm, and hsm2) to new VMware VMs running CENTOS6 with just one volume (store)....and have to correct the mailbox IDs after migration. Basically looks like this...
- backup briefcase/documents to TGZ file (I occasionally get corrupt/missing documents after migration)
- zmblobchk and cleanup
- migrate account
- correct mismatching mailbox IDs in the MySQL table
- reindex account
Later on if the user finds they have missing/corrupt documents, restore them from the TGZ file we took.
I'll just warn you ahead of time that I'm no professional programmer. :)
Matt Mencel
Western Illinois University
From: "Tim Ross" <tross@calpoly.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 6:41:46 PM
Subject: Re: Migrating accounts and HSM volumes
Tony,
Thanks for the comments. I got a bit confused at the end of your note, though. What has been know to work in all the cases you've seen so far?
From: "Tony Publiski" <tonster@tonster.com>
To: "Tim Ross" <tross@calpoly.edu>
Cc: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 4:31:20 PM
Subject: Re: Migrating accounts and HSM volumes
Hi Tim,
Unfortunately, you won't be able to simply drop in a new zmmboxmove file. Support does have a script that can be used to assist in recovering from accounts that have been moved already, but you'll need to upgrade to avoid this. I wouldn't suggest just relying on the script to get you out of this and buy you time until you can upgrade, as it has not been tested with long-term use like that. It's known to work in all the cases we've seen so far though.
From: "Tim Ross" <tross@calpoly.edu>
To: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 7:04:56 PM
Subject: Re: Migrating accounts and HSM volumes
Ryan,
I think you are right. That bug sounds exactly like the problem. Unfortunately, I can't upgrade the old and new systems at this point, so maybe Zimbra will be able to give me an updated zmmboxmove file I can use.
Thanks,
From: "Ryan Tandy" <rtandy@sd63.bc.ca>
To: "Tim Ross" <tross@calpoly.edu>
Cc: "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca>
Sent: Monday, August 19, 2013 3:46:47 PM
Subject: Re: Migrating accounts and HSM volumes
Hi Tim,
On 13-08-19 03:20 PM, Tim Ross wrote:
> Unfortunately, neither of these processes apparently reset the Volume ID
> associated with each mail item. So, we end up with some folders or
> messages that can't be accessed and give a "No Such Volume" error when
> clicked.
If I've understood you correctly and you're currently running 7.2.x,
that sounds like http://bugzilla.zimbra.com/show_bug.cgi?id=79581 which
luckily should be fixed in the next point release...
--
Ryan Tandy - Programmer/Analyst rtandy@sd63.bc.ca
School District 63 (Saanich) +1 250 652 7385