#59 Incomplete base backup

[Gregory X]

We recently attempted to restore a base barman backup of a PostgreSQL production server onto a development server. The remote restore was performed using the barman recover command. Barman reported the restore as being successful. After the restore, running vacuum full verbose analyze on the PostgreSQL development server resulted in this error:

ERROR: could not open file "base/16421/41636": No such file or directory

The 41636 file does not exist in the base sub-directory under the backup set on the Barman server. However, 41636 does exist on the PostgreSQL production server, and in every other backup set on the Barman server. It was clearly missing from the backup that was restored. The barman log doesn't contain any errors for the backup with the missing file. Why would barman consider an incomplete backup to be successful?

The backup and restore were performed using barman 1.3.0. The PostgreSQL version is 9.3.4.

[Gabriele Bartolini]

Hello,

version 1.3.0 is a 1 year old version. We can only afford to maintain the latest stable release of Barman.

Consider that several bug fixes have been done since then. Would it be possible for you to verify the bug still persists with a more recent version? Could you please try with version 1.3.3 or - possibly - 1.4.0-alpha.1?

Thanks,
Gabriele

[Gregory X]

Hi Gabriele,

We upgraded to version 1.3.3 after the issue occurred with the incomplete backup. I'm not aware of any issues with 1.3.3 restores. We've been on 1.3.3 for a little over a week.