Virtual disk size is not a multiple of 1KB
| KB ID: | 1848 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x 7.x, 8.x, 9.x |
| Published: | 2014-01-09 |
| Last Modified: | 2020-08-13 |
| Languages: | FR |
Challenge
Backup Copy job might fail with error:
Inline data validation detected that the target backup file is corrupted, but correction has failed
Restore job might fail with error:
Declared and actual sizes of the disk […] are different. Declared size: […]. Actual size: […]
Inline data validation detected that the target backup file is corrupted, but correction has failed
Restore job might fail with error:
Declared and actual sizes of the disk […] are different. Declared size: […]. Actual size: […]
Cause
VMDK disk is not properly aligned. A disk is not properly aligned when the size of the disk is not a multiple of 1KB.
VMware does not allow creation of unaligned disks via Graphical User Interface.
Usually unaligned disks are result of P2V conversion, or disk creation via vmkfstools utility.
VMware does not allow creation of unaligned disks via Graphical User Interface.
Usually unaligned disks are result of P2V conversion, or disk creation via vmkfstools utility.
Solution
Please use vmkfstools utility to extend and align the disk. Increasing the size of a virtual disk (1004047)
If the disk in question is presented as a virtual RDM, use the SAN software to properly resize the LUN. Expanding the size of a Raw Device Mapping (RDM) (1007021)
Afterwards run Backup job and make a full backup of that VM.
If the size for one of the disks on the VM is not a full integer (ex. 80.3423432 GB) increase the size of the disk within the VM configuration to a full integer (ex. 81 GB).
In some cases this error may occur on a VM whose disks is already a full integer (ex. 80 GB), try increasing the disk size to next full integer (ex. 81GB) and run the Veeam job again.
If the disk in question is presented as a virtual RDM, use the SAN software to properly resize the LUN. Expanding the size of a Raw Device Mapping (RDM) (1007021)
Afterwards run Backup job and make a full backup of that VM.
If the size for one of the disks on the VM is not a full integer (ex. 80.3423432 GB) increase the size of the disk within the VM configuration to a full integer (ex. 81 GB).
In some cases this error may occur on a VM whose disks is already a full integer (ex. 80 GB), try increasing the disk size to next full integer (ex. 81GB) and run the Veeam job again.
| KB ID: | 1848 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x 7.x, 8.x, 9.x |
| Published: | 2014-01-09 |
| Last Modified: | 2020-08-13 |
| Languages: | FR |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
