Agent-based backup of Windows, Linux, Max, AIX and Solaris machines.
Post Reply
hjk85
Lurker
Posts: 2
Liked: 1 time
Joined: Apr 28, 2026 3:49 am
Contact:

failing with "Block is not initialized" during incremental backup

Post by hjk85 »

<support case ID : #08071870>

Code: Select all

Error: Block is not initialized.
Failed to download disk 'a62b2799-2320-4880-81bb-36ce0c5046e8'.
Reconnectable protocol device was closed.
Failed to upload disk.
Skipped arguments: [EmulatedDiskSpec>];
Agent failed to process method {DataTransfer.SyncDisk}
Hello.

For the past few days, the backup has not been proceeding due to the error shown above.

I confirmed on forums and communities that this error can be resolved by performing an active full backup. While the active full backup and the subsequent first incremental backup succeed, the same error continues to occur from the next incremental backup onwards, causing the backup to fail.

And I have checked the health of the physical disks on the server, and all disks are confirmed to be in normal condition. There are no hardware-related errors or bad sectors detected.

Also, is there anything else I should check?

Thanks.
david.domask
Product Manager
Posts: 3641
Liked: 884 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: failing with "Block is not initialized" during incremental backup

Post by david.domask »

Hi hkj85, welcome to the forums.

Thank you for sharing the case number and sorry to hear about the challenges. Please wait for Veeam Support on this case, as the error can unfortunately have many causes and will require review of the debug logs in order to better offer troubleshooting.

I see that the case was opened as a Free case, meaning support is provided on a "best-effort" basis. If you have a paid license with an active support contract, I advise opening the case as licensed case. If you are unable to open cases with your active license, please see KB2211 and ensure you're set as a Case Administrator.
David Domask | Product Management: Principal Analyst
hjk85
Lurker
Posts: 2
Liked: 1 time
Joined: Apr 28, 2026 3:49 am
Contact:

Re: failing with "Block is not initialized" during incremental backup

Post by hjk85 » 1 person likes this post

Unfortunately, the Veeam support case was closed due to a "shortage of support personnel."

The following is the process I followed to resolve the error, and I ultimately achieved a "successful backup."

1. Merge all numerous Hyper-V snapshots on the backup target server.

2. Reinstall the Veeam Agent on the backup target server.

3. Enable Skip Bad Blocks in the Registry Editor on the backup target server.
regedit - HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
NEW DWORD - SkipBadBlocks - 1
Services - Veeam Agent for Microsoft Windows - Restart

4. Create a new backup job.

5. Disable "Enable application-aware processing" in the backup job settings.
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests