Good day
i have had the misfortune of a failed Zimbra upgrade attempt having to recover from a broken backup.

The background:
While Zimbra was being upgraded from 8.0.7 to 8.7.1 the upgrade failed halfway through creating a new database. Not realizing the database was not being backed up and having to recover from an old backup due to various reasons (ran out of disk space), I ended up with an account (admin) that was recovered into a new account, breaking original admin account.

I deleted this DB entry, but it was linked to a GAL entry, and had to be re-injected.

When I run the blobcheck I get a:
Code:
com.zimbra.common.soap.SoapFaultException: no such account: d7cc5aa2-ff54-4042-a8bb-df679a22703f
ExceptionId:qtp853768135-18346:https://127.0.0.1:7071/service/admin/soap/CheckBlobConsistencyRequest:1497508674649:e637ad49ec350008
Code:account.NO_SUCH_ACCOUNT
        at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:88)
        at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:333)
        at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:308)
        at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:255)
        at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:167)
        at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:386)
        at com.zimbra.common.soap.SoapTransport.invokeWithoutSession(SoapTransport.java:372)
        at com.zimbra.cs.account.soap.SoapProvisioning.invokeRequest(SoapProvisioning.java:442)
        at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:450)
        at com.zimbra.cs.store.file.BlobConsistencyUtil.checkMailbox(BlobConsistencyUtil.java:244)
        at com.zimbra.cs.store.file.BlobConsistencyUtil.run(BlobConsistencyUtil.java:201)
        at com.zimbra.cs.store.file.BlobConsistencyUtil.main(BlobConsistencyUtil.java:328)
Will migrating the system release this broken entry?

kind regards
aubrey