As the machine needs a full OS refresh (that Debian release is not supported any more, and Debian is dropping out of your supported OS list completely anyway) I thought that a completely fresh install (latest stable Zimbra (7.1.3) on Ubuntu 10.04) followed by a migration would be the path of least resistance, though that may have been a bad assumption.
Following the notes at http://blog.zimbra.com/blog/archives/2008/09/zcs-to-zcs-migrations.html]Ã‚Â» Zimbra :: Blog I have run
/opt/zimbra/bin/zmmailbox -z -m email@example.com getRestURL "//?fmt=tgz" > user.tgz
for each account on the old server, transferred the files over, created the accounts, and then run
/opt/zimbra/bin/zmmailbox -z -m firstname.lastname@example.org postRestURL "//?fmt=tgz&resolve=reset" ./user.tgz
The tgz files seem to be of the sort of size I would be expecting, and no errors are reported (aside from first time around when I hit a "request too large" message fixed by increasing the maximum request size in the admin console), but nothing seems to import where the user can see it (no mail, no folders, no calendar information).
The command takes a while to think, and the account's used quota value goes up by a chunk, and the space used under /opt goes up, so something has happened. If I run the same import command again the user's quota goes up again, so it would seem that the data is being stored somewhere instead of being processed as an import?
Is there something obvious that I'm doing wrong?
I'm going to try rebuild the destination machine from scratch, if only to get rid of the space consumed in /opt (which doesn't seem to be released when the relevant account is deleted) then try again, but any pointers as to what logs are relevant for finding what happens (the command outputs nothing to stdout or stderr), or pointers to what I'm missing (if I'm doing something wrong) would be appreciated.
(plan B is to upgrade rather than reinstalling on the new architecture and migrating: 1. upgrade to latest 6.0.x, 2. migrate the whole lot from Debian/x86 to the new VM running Ubuntu/a64, 3. upgrade to 7.1.x - but that may take far longer if only as I'd probably backup the whole VM(s) at each step for paranoia's sake, and I'm told there are extra complications with a jump from x86->a64)