The version does not support this version of the file format, 0xC03A0005
The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files here— If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is, one that keeps expanding depending on the backup size. The problem occurs only in the case of File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.
The only viable solution is to use Strict Allocate: option in the smb.conf file
Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.
What does this option do?
According to the official website, You can also test if the VHD file is a sparse file by manually mounting it. Open the Disk Management tool and click “Action” and then “Attach VHD” and then specify the path of the vhd file. If the error is the same as you get for the backup then it is because of the sparse file. I hope the post was easy to follow, and you were able to resolve the 0xC03A0005 error code related to Windows backup over to the NAS.
