Secondary GPT header LBA 209715199 exceeds the size of the disk (86401630720)

Did you check the logs to see if there was more details - C:\ProgramData\Veeam\Backup

Never seen this message before. Maybe support case?

Hi @CarySun, I’ve found an old post here https://forums.veeam.com/vmware-vsphere-f24/secondary-gpt-header-lba-692060159-exceeds-the-size-of-the-disk-268435456000-t73035.html

You can try referring to that case id 04714989, although it doesn't seem to have been resolved..

YA, I saw this, but it seems not to be resolved, it rebuilt the VM.

@CarySun , as @coolsport00 sugested, it could be related with space in mount server.
Did you check if you have enought space?
I found this on Veeam Forum https://forums.veeam.com/vmware-vsphere-f24/secondary-gpt-header-lba-692060159-exceeds-the-size-of-the-disk-268435456000-t73035.html, but no solution so far.

Sometimes when i have this problem, i restore the VM using the instant recovery, when online without network interface,  Add a New disk to VM > bring it online > Format using disk managment and select a Letter, example i:\.
This way you can copy what you want to this new disk, after that you can shutdown this VM, remove the disk (Do not delete from datastore) and mount in another server it can be on a veeam proxy you are not using.

@coolsport00 Interesting, it seems as you thought. This VM has only one virtual disk (C:) and it has 9GB of free space. I cannot restore file (actually, I cannot mount any restore point to the mount server) from any existing restore points.

I tried to create a new test backup job to backup the VM and tried to restore from the first restore point (full backup), but got the same error. So I expend the C drive to add 10GB more space to it, then rerun the backup job.

Now, I can mount the incremental restore point but I still cannot mount the full backup restore point.

That means all of the restore points cannot be mounted before expanding the C drive of the VM.

@HenriqueA Ya, it’s a good idea to restore files. I also can use the Restore VM file function and mount it to the existing VM as a new virtual disk drive. I just want to find the root cause.

Thank you!

@CarySun yeah..thought something like that was in play.