Backup Copy to CC Corrupted

[mingji]

Case # 05700222

FLR and Instant Recovery are still working, but VM/vdisk recovery fail on 2 vidks with error "Failed to decompress LZ4 block"

Passed Validator check, but health check found corruption:
Disk Isthmus-aklfile1-HSR_2-flat.vmdk on host Isthmus-aklfile1-HSR is corrupted. Possible reason: Storage I/O issue. Corrupted data is located in the following backup files: Isthmus-aklfile1-HSRD2022-11-04T210158_2B57.vbk

Veeam support checked job logs then pointed out that Veeam skipped oib repair because it can't find encryption key. However, the backup copy job
and source backup job are not encrypted.
Due to the size of VM (37 TB full backup), it's almost impossible to run another active full backup copy (will take 3 months to transfer)
Please help us to find a way to repair the chain.

[Gostev]

Actually this is not a support forum, so unfortunately we cannot help you here over forum posts. You should continue working with our customer support organization. Thank you!

[Gostev]

P.S. I would definitely recommend replacing that misbehaving backup storage before going for another active full backup copy. Otherwise it's only a matter of time before you will run into the same issue again.

Also, remember you can use backup seeding by shipping an external storage device to avoid performing initial backup copy over the network.

[mingji]

Actually this is not a support forum, so unfortunately we cannot help you here over forum posts. You should continue working with our customer support organization. Thank you!

Thanks for the reply Gostev, I apologize for posting it here. Are you able to move this thread to Veeam B&R forum?

[veremin]

It's been moved, but the investigation should continue via support ticket. Thanks!