Veeam Backup Validation Tool

I ran across an issue with my VM backups saying that they were failing validation and not backing up properly, even though each VM showed success when checking the logs. I was getting a specific error in the backup logs:

Backup files health check has been completed
Failed to perform backup file verification Error: Data error (cyclic redundancy check). Failed to read data from the file [B:\Backups\LDLNET Other Backup\LDLNET BackupD2019-01-12T001234.vbk]. Agent failed to process method {Signature.FullRecheckBackup}.

So, I did some research and found a little known tool that is used to manually validate the Veeam backup files, basically because it’s a tool usually executed only by the technical support staff. It is located in the following folder (Version 9.5.0.1922):

C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Validator.exe

Its main use case is to verify the consistency of a backup created with Veeam Backup & Replication. It’s NOT SureBackup, that does another kind of control by starting the VM from the backup file, and is for sure more reliable. But if you do not want to start a SureBackup activity, or if you only have a Standard license lacking SureBackup, this tool can be a good alternative, or you can use it to check a backup file after it has been moved or if you had a consistency problem on the storage holding those files.

The command switches are listed here for the executable

Now since I had a specific file that was showing an error, I wanted to run the command against that file to validate the backup. Here is the command that I ran:

.\Veeam.Backup.Validator.exe /file:”B:\Backups\LDLNET Other Backup\LDLNET BackupD2019-01-12T001234.vbk”

It started running against the file and it did fail as it did in the log files from the backup process. Here is the error message:

Skipping VM ‘B:\Backups\LDLNET Other Backup\LDLNET BackupD2019-01-12T001234.vbk ‘: File “LDLNET-VM01-flat.vmdk” is corrupted. Data error (cyclic redundancy check).
Failed to read data from the file [B:\Backups\LDLNET Other Backup\LDLNET BackupD2019-01-12T001234.vbk ].

Now, when looking at the backup job, I found that the file listed was the original full backup that I had completed when I originally changed the job for all the new VMs that were now listed in the backup job. Since that was the case and I did not have any VMs that were in a bad state, I deleted all the backup files from my storage and started another full backup of the VMs in the job.

Using the CLI tool to manually validate the backup file was very helpful in this case as it would help me decide to clear out a backup that would not restore properly, even with the incremental backups since the base full file was corrupt.

References:
Veeam Backup Validator: check the consistency of your backup files

VCSServiceManager.msi

LDLNET LLC - Life In Action! Your Source for Professional IT Services!

Let me just say that file is possibly: THE WORST FILE THAT EVER EXISTED ON THE FACE OF THIS EARTH! 

I have had the absolute worst experience trying to install VMWare vCenter Server 6.x onto my Windows Server at the house. I didn’t really have any issues with installing vSphere 6.7 on my HPE Proliant DL360 g6 server so that I could update my environment. I was going to put vCenter on as well so that I could keep my servers updated and such.

The main issue with the install is that it fails when installing the VCSServiceManager.msi component with a 1603 error. Needless to say, this has been a major issue that started with version 6.0. I have looked through all of the following articles in my search to remediate this issue:

I’ve looked through more than that honestly and was NOT able to get past that part of the install, now I did install the msi separately, and the main install acted like it finished successfully, but none of the services installed on the server and the vCenter Component was basically non existent when trying to access it. I even went through setting up an Microsoft SQL Server Express back end thinking it might be an issue with the Python SQL component that comes with vCenter. I even formatted my Server OS and started from scratch. No luck what so ever on the installation. I bet I spent 30 man hours over the course of a week or two trying install after install.

Seeing that it is the evaluation version, I cannot seek direct help from VMWare as their support is paid support, but being an IT guy myself, and seeing all the problems with that part of the install, leads me to believe that I wasn’t the problem when I was installing the software. I followed all the processes to get the installation to go smoothly and correctly, but did not succeed.

I used to be a real advocate for VMWare as a great Hypervisor, but, I will be migrating to Hyper-V now. I’m running all 2019 servers anyway, I should have Hyper-V on my host.

Question: Has anyone had issues with Hyper-V or Server 2019 Datacenter on an HPE Proliant DL360 g6 server? I haven’t seen too much issue from my research. So if the blog is down this weekend, you’ll have knowledge why as I convert my VMs to VHDX disks and get Hyper-V setup.

Happy Reading! Please leave some feedback!