It broke the symlink because it thought it was a new install and therefore created a new dir - we'll see if we can investigate why
He's a NE customer (tufts.edu) and this is kinda his home testbox; even with nothing 100% cirtical on it we'll still get it .9>.10 perfectly fine/ok/won't loose a thing of his testing accounts. (a regular mount will solve it)
He had made a tar backup while there we're still plenty of zimbra processes running (instead of an rsync etc) so we're just finishing up on getting that that 4.5.9 backup restored and running.
! >
Open Source Edition Backup Procedure - Zimbra :: Wiki
A couple of months back there was a cluster install case
Bug 17032 - clarify cluster mountpoint symlink behavior Bug 17891 - New-style cluster install: put zimbra home on shared disk