backup active full or first full success but restore error

[siranee.ja]

Hi Everyone,

I use veeam 9.5 u4. I have one vm have 3 disks, first disk is vm boot disk 40G, second disk is vm data disk 150G, third disk is vm data disk 500G.
I formatted repository to NTFS 4k block as default.
I started full backup this vm and it successfully backup but when I restored to the different location it's error bad crc.
I formatted repository to NTFS 64k block as recommend.
I started new full backup this vm and it successfully backup and this time I restored successfully.
After I backup incremental for a while and verified with verify command line , it error bad crc again. Even backup active full , it still error bad crc.
I formatted repository to NTFS 64k block again.
I started new full backup this vm and it successfully backup but when I restored to the different location it's error bad crc as well as verified with verify command line , it error bad crc again.

Last time error
Validate error : Skipping VM 'sysauranuch': File "sysauranuch_2-flat.vmdk" is
corrupted. Failed to decompress LZ4 block: Bad crc (original crc: ec1cb520, current
crc: f23898cf).

Restore error: 8/5/2562 7:51:44 Error Restore job failed Error: Failed to
decompress LZ4 block: Bad crc (original crc: ec1cb520, current crc: f23898cf).
Failed to download disk.
Agent failed to process method {DataTransfer.SyncDisk}.


Anyone has problem like this before? Any suggestion to solve the problem?

Best Regards,
Siranee Jaraswachirakul.

[foggy]

Hi Siranee, please contact technical support for a closer look. To me it looks like the storage issue though.

[siranee.ja]

Hi Alexander,

Thank you for your suggestion. Yes, I already open the Case # 03547326.
I already checked the storage issue but it seeemed healthy.
If anyone has the same problem as me, we can share the experience.

Best Regards,
Siranee Jaraswachirakul.

[siranee.ja]

Hi All,
Finally, I found that it's about the problem on the physical server. I migrated veeam server from the old physical server to the new physical server. The backup full didn't be corrupted anymore and can restore successful.

Best Regards,
Siranee Jaraswachirakul.
Top