The backup job cannot write to the destination because it uses a sparse file system
Error code |
Product |
Applies to |
---|---|---|
BA392 |
BackupAssist |
BackupAssist v9 and later |
Description
This error will occur when a System Protection backup on a Windows Server 2012 or Windows Server 2012R2 Server tries to back up to a network destination that has a sparse file system.
Resolution
There are 3 possible resolutions for this problem
Resolution 1 - Use a Data container
Modify your backup job so that it uses a Data container on the backup destination. The backup job will write to the Data container's file system, which is supported.
To add a Data container:
- Open BackupAssist.
- Select Manage Backup Jobs
- Select the backup job.
- Select Edit from the top menu
- Select Destination from the options on the left
- Click on the Select new destination option at the top
- Select Enable Data container.
- Select Next until to come to the Data container volume settings screen
- Set the Data Container size or allow the Data container to grow into the space available. If your backup destination is using a sparse file system, the Data container should not exceed 2TB in size.
- Select Finished
To learn more about Data containers and how to use them, see our Data Container guide guide.
Resolution 2 - Turn off sparse files on the NAS
Turning sparse files off on your NAS device can resolve the problem and allow the System Protection backup to use the NAS as a backup destination.
To learn more, see our Custom access policies for AWS guide.
You should also check that the NAS drivers and firmware are up to date. The drivers and firmware will be available from your NAS vendor.
Resolution 3 - Remove the sparse file system
Upgrade the NAS device (firmware or hardware) so that it is no longer a sparse file system. For information on how to perform this task, refer to the NAS device's documentation.
To learn more, see our Custom access policies for AWS guide.
Last updated |
Created |
Further assistance |
---|---|---|
15th May 2017 |
24th Jul 2015 |
BackupAssist Support page |