Fix "The Version Does Not Support This Version of the File Format" Error

Posted by @Cody

July 29, 2015

Solutions to fix the error: The version does not support this version of the file format, received while backing up to NAS device or to local disks.

The Scenario

When backing up file or system state to a shared folder on Network Attached Storage (NAS) device with windows built-in backup tool on Windows Server 2003/2008/2012 (R2)/SBS 2003/2008/2011 or Windows 10/8.1/8/7/XP/Vista, you may receive the following error:

"The backup of volume xxx could not be completed, Error: the version does not support this version of the file format."

When backing up to local disk, you may also encounter the error:

"There was a failure in preparing the backup image of one of the volumes in the backup set (0x807800C5). Additional Information: the version does not support this version of the file format. "

Format Error

The Cause

Sparse files are universally used for taking backups, as it saves disk space and reduces time. When backing up data to NAS storage device, Windows Backup will create a mounted .VHD file, but the native VHD driver does not support the .VHD file created as a sparse file. Therefore, the backup failed.

If you use both “include” and “exclude” in one Wbadmin command to perform the backup, you may get this error.

The existing old Windows backup files in the destination location can also lead to this error.

The Solution

To fix the problem of being unable to backup to NAS, you can try the methods below.

1. Check on your NAS to see if the file is a sparse file. If it is a sparse file, you can modify or add a thread, "strict allocate = yes", which will force it not to create sparse file.

1.1. Delete the existing files on the backup destination location to make sure Window backup will create a new backup file.

1.2. Log in the NAS.

1.3. Open the smb.conf file (usually in the [global] section of /etc/samba/smb.conf, or /etc/config/smb.conf). You may whether not find the "strict allocate’ line or find the “strict allocate = no”

1.4. Modify or add a thread, "strict allocate = yes" to the smb.conf file. Then save it and exit.

1.5. Reboot your system to restart the service. Then you should be able to backup to NAS with Windows built-in backup tool. If you don not want to reboot system, log onto the NAS and run the following command:/etc/init.d/services restart.

2. Check the backup command if you use Wbadmin command to backup. If you set an “include”, then it will backup everything in the “include” and ignore anything not in the “include”. Hence, make sure the command you used do not have “include” and “exclude”.

Syntax for Windows Vista and Windows Server 2008 shows as below:

wbadmin start backup

[-backupTarget:{<BackupTargetLocation> | <TargetNetworkShare>}]

[-include:<VolumesToInclude>]

[-allCritical]

[-noVerify]

[-user:<UserName>]

[-password:<Password>]

[-noinheritAcl]

[-vssFull]

[-quiet]

Syntax for Windows 7 and Windows Server 2008 R2 and later version: only changed [-vssFull]

to [-vssFull | -vssCopy]

3. Rename or delete the folder from “WindowsImageBackup” in the location where you chose to save the backup images.

4. If you still get the error that the version does not support this version of the file format through those steps or you want a better Windows backup solution, you can use AOMEI Backupper to complete your backup task. With its great compatibility with NAS, Backupper enables you to backup to NAS or restore from NAS in Windows PCs and Servers smoothly. With its concise interface and humanized design as the screenshot below, you can hardly encounter an error while using it.

Server Backup

Besides, Backpper has implemented many useful features, such as migrating operating system (OS) with system clone, performing offline restore via bootable media or AOMEI PXE Tool, restoring system to dissimilar hardware machines and more. Now you can download the free backup software for Windows PCs or the thirty-day trial version for Windows Servers.