File corrupted from proxmox-backup-client mount. Not from Web GUI

Nov 4, 2022
2
0
1
Hi,
Hope you're having a nice day.

client version: 2.1.1 and 1.1.14
server version: 2.1.5


Backup and restore with proxmox-backup-client Linux Client (Debian 9/10). Not from PVE.



We recently have to restore multiple website from multiple backup. Each of our web server hosts about 10 websites.

For re-deploying as many website as possible faster, we restore each website without images/videos. The solution for this was to mount backup from each web server thanks to proxmox-backup-client mount and then use a rsync command with exclusion option.


Unfortunately some web site prompt errors. In fact some file weres corrupted :

PHP Parse error: syntax error, unexpected end of file in ....

When we open up file in vi/vim the end of the file looks like this :


PHP:
.....

if ( ! $block_type->attributes ) {


                $block_type->attributes = array();


        }



        if ( $has_color_support && ! arr^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@.....


The problem also happen when we try to open a file directly from the proxmox-backup-client mount "environment". The first result is from a regular file :


Bash:
$~ file elements.php

elements.php: PHP script, ASCII text


$~ file colors.php

colors.php: data


In addition, this problem appears only on the same few files. But always the same file. But not all the time, the file wasn't corrupted on certains website.

After this problem solved, we copy our images, but there were also broken, like half of the image was good but the other half was black.

For images, when we use command from imagick for getting Metadata of the image, at the end we got this message :


Bash:
$~ identify -verbose c90e0cc1346dd39a089b3324e16efdb2.jpg

Image: c90e0cc1346dd39a089b3324e16efdb2.jpg

  Format: JPEG (Joint Photographic Experts Group JFIF format)

....

identify-im6.q16: Premature end of JPEG file `c90e0cc1346dd39a089b3324e16efdb2.jpg' @ warning/jpeg.c/JPEGWarningHandler/386.

identify-im6.q16: Corrupt JPEG data: premature end of data segment `c90e0cc1346dd39a089b3324e16efdb2.jpg' @ warning/jpeg.c/JPEGWarningHandler/386.


Our last way to resolve this issue was to use proxmox-backup-client restore directly on the Proxmox Backup Server and then rsync (With checksum option for overwrite corrupted images) from PBS to our Web server to have all our image working (Each web-server contains around 600G of data, so we can't restore specific image by hand from GUI).

Is there a better/safer way to restore a specific folder or exclude folder from the "proxmox-backup-client restore" command line like with rsync ?
Or the method with mount is the good one but why does some file are corrupted ?

Thanks in advance !
 
Ok, thanks for the quick response ! We will check with 2.2.6 version.

BTW is there a way to use the regular restore but with a directory exclusion ? Or it is not possible ATM/In future ?

Thanks !
 
the catalog shell might be an alternative. nowadays there's also 'proxmox-file-restore', but that was introduced during the 2.x series as well..
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!