I recently restored a Linux cloud VPS and I experience the issue that their are some corrupt files in the backup.
These files will have their original file size (for instance 25 KB) but they are just filled with the NULL character, the ^@ in VI or just all 00 in hex format.
The cloud VPS was running on Digitalocean (KVM virt) with CentOS 7 x64 and 1 disk with ext4 filesystem.
I was using Veeam Agent for Linux GA and backing up to a VBR 9.5 U1 on a ReFS disk over a OpenVPN tunnel with TAP interface.
The first file I found was a static config file of the OpenDKIM daemon on the system (KeyTable) which was the culprit of the malfunctioning of my outgoing mailfow.
The second file I found was a CSS file from a web application.
After that I went hunting for such files on the system:
- found a corrupt binary, it was "/usr/sbin/httpry". A simple "yum reinstall httpry" fixed that.
- found 3 corrupt php files and 2 corrupt xml files from the phoronix-test-suite. A simple "yum reinstall phoronix-test-suite" fixed those 5 files.
it goes on and I found corrupt files from nmap, webmin, alsa-firmware, php-tcpdf, some image files, ...
One could argue that the corrupt files existed on the cloud VPS, but I know for a fact that the web application was fine and after restore it was not showing properly because of the corrupt CSS file.
Anyone seen this behavior before?