Retrieved less bytes from the storage than required

KB ID: 2255
Product: Veeam Backup & Replication
Version: 9.x
Published: 2017-03-07
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Backup or Backup Copy Job fails with the error: “Retrieved less bytes from the storage [0] than required”.

User-added image

Cause

The point may or may not actually be present on the repository when you browse the storage itself. However, the key issue is that the point shows up as 0 B / Incomplete under the properties of the backups (navigate to Backup & Replication > Backups > Disk, then right-click and select the properties of the backup in question).

User-added image

As shown, the Data Size/Backup Size both report 0 bytes of data, and the restore point is flagged as Incomplete. However, as shown below, the restore point file can exist on the storage with a non-zero file size:

User-added image

In very few situations, the contents of the affected backup file may be partially recoverable. However, this prevents us from continuing the chain with the incomplete restore point.
 

Solution

  1. Ensure the job is stopped and disabled.
  2. Manually delete the point in question directly from the Repository using Windows File Explorer. Ensure this is the correct file.
  3. Rescan the Repository under Backup Infrastructure. (https://helpcenter.veeam.com/backup/vsphere/rescanning_backup_repositories.html)
  4. Have Veeam forget the missing restore point. (https://helpcenter.veeam.com/backup/vsphere/remove_missing_point.html)
  5. Re-enable and run the job.
In the event these steps do not resolve the issue, it may be necessary to start with a new active full backup, or in a worst-case scenario, to have Veeam remove the current backups from configuration (not from disk; the chain is likely still viable for restores) and start the chain anew. Support can help you to review any options from this point.
 
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.