We're trying to restor a particular user's mailbox but we get an error message. This is after something happened and all his contacts were "messed up", the phone numbers and other data were copied or moved between contacts apparently at random.

This is the error message we get when running zmrestore on the mailstore server with the debug option turned on:

Code:
Error occurred: system failure: Unable to parse XML file /opt/zimbra/backup/sessions/full-20100723.230012.217/accounts/1ae/4f2/1ae4f258-3b62-498f-a2d6-c3f419a9807c/ldap_latest.xml
class=com.zimbra.common.soap.SoapFaultException
message=system failure: Unable to parse XML file /opt/zimbra/backup/sessions/full-20100723.230012.217/accounts/1ae/4f2/1ae4f258-3b62-498f-a2d6-c3f419a9807c/ldap_latest.xml
mIsReceiversFault=true
mIsLocal=false
mDetail=<soapetail><Error xmlns="urn:zimbra"><Code>service.FAILURE</Code><Trace>btpool0-2337://localhost:7071/service/admin/soap/RestoreRequest:1280472209960:1f34dc6aa019c0e1</Trace></Error></soap:Detail>
mFault=<soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text>system failure: Unable to parse XML file /opt/zimbra/backup/sessions/full-20100723.230012.217/accounts/1ae/4f2/1ae4f258-3b62-498f-a2d6-c3f419a9807c/ldap_latest.xml</soap:Text></soap:Reason><soapetail><Error xmlns="urn:zimbra"><Code>service.FAILURE</Code><Trace>btpool0-2337://localhost:7071/service/admin/soap/RestoreRequest:1280472209960:1f34dc6aa019c0e1</Trace></Error></soap:Detail></soap:Fault>
We even did a full backup of this account and tried restoring from that and it didn't work. We tried restoring other users and they seem to work, the problem is this account.

This is what we're seeing in the log file:

Code:
com.zimbra.common.service.ServiceException: invalid request: restore is still in progress
ExceptionId:btpool0-5352://localhost:7071/service/admin/soap/BackupRequest:1279789400470:a94b718c68360a69
Code:service.INVALID_REQUEST
        at com.zimbra.common.service.ServiceException.INVALID_REQUEST(ServiceException.java:254)
        at com.zimbra.cs.backup.BackupManager.setCurrentOp(BackupManager.java:911)
        at com.zimbra.cs.backup.BackupManager.startBackupFull(BackupManager.java:175)
        at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:129)
        at com.zimbra.cs.service.NetworkDocumentHandler.handle(Unknown Source)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:272)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
        at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:324)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:525)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
but enough time has passed that the restore should/could have finished.

Is there a way to force a restore to finish? would that solve it? is this just a symptom of a bigger problem.

thanks