[SOLVED] Restore problems since upgrade

[stuartg.orion]

Hi all, I recently (1 and a half weeks ago) upgraded our server to version 5.0.4 from version 5.0.2. I have just tried to restore an account from a full backup 5 days ago and received the following error:

Error code: service.FAILURE Message: system failure: Unable to process files of backup version 5.3; expected 7.0 Details:soap:Receiver

The upgrade went well at the time and all backups seem to be running correctly.

Any thoughts why this is happening? And how I could fix it? Has anyone else done a restore after a similar upgrade?

Thanks

Stuart

[mmorse]

We currently don't intend restore between different versions - though there is some enhancements being worked on.
Think this one was intended for minor version's: Bug 14002 - Add conversion tool to upgrade backup versions to allow restore on later zcs versions
And the tougher: Bug 15750 - support for restore across major versions

While it goes without saying to take a full backup before you upgrade, it's also good practice to take a full immediately after upgrading (so you have a 'fresh' & because those old backups generally aren't useful anymore unless you install a box with a prior version somewhere).

[stuartg.orion]

I understood that I couldn't restore from a pre-upgrade backup but I have a full backup from after the upgrade which gives that error. Is it because I still have old backups there as well?

What's the best practice to clean out the backups after an upgrade?

[mmorse]

Ah, your wording had me thinking you we're trying to restore a 5.0.2 on a 5.0.4

Options:
A) Clear your /opt/zimbra/backup/tmp/ then try the restore again.
or
B) Upgrade to 5.0.5 which has the fix for: Bug 26933 - Restore fails with version mismatch errror: "Unable to process files of backup version 5.3; expected 7.0"

Restore can create a data file containing blob digest to path mappings for shared blobs. If such a file was created in ZCS 4.5.x and the server is upgraded to ZCS 5.0.4, a subsequent restore will get version mismatch error because of a bug in version comparison code.

5.0.5 is Released!
-For safety wouldn't hurt to make a copy of your /opt/zimbra & any linked directories in addition to a 'zmbackup -f -s server -a all' if you got the space. I like to play it safe whenever I have the ability

[stuartg.orion]

Thanks heaps Mike, option A did the job. Sorrry about the wording confusion.

Yeah space is always an issue - we've just purchased a SAN so hopefully when next I upgrade I'll have a bit more free capacity.