BA1310: General hardware failure¶
End of life
BackupAssist v8 and later don't use NTBackup. This article applies to BackupAssist v7 and earlier, which reached end of life on 30 September 2016 and no longer receive technical support. See Software end of life.
| Error code | Product | Applies to |
|---|---|---|
| BA1310 | BackupAssist | BackupAssist Version 4 |
Description¶
The device reported an error on a request to write data to media.
Error reported: Unknown error.
This error indicates a scheduling conflict. Certain other programs can interfere with BackupAssist if they are running at the same time.
Resolution¶
Resolution 1. Scheduling issues (Unknown error)
This section explains VSS and device conflicts. Refer to the section applicable to your issue.
VSS conflicts: Having two backup jobs running at the same time within BackupAssist can cause errors if both backup jobs are trying to run VSS. Ensure that only one backup job is running at any one time.
Hardware conflicts: Conflicts with backup devices can occur when another process is trying to use the backup destination at the same time as BackupAssist. Make sure that there are no scheduled tasks, particularly backup tasks, that run at the same time as your scheduled backups.
To confirm that this is a scheduling issue try running a backup during the day, or try changing the scheduled time of your backup by a few hours. If these backups work, the problem is likely to be a scheduling conflict.
Resolution 2. Windows error (Unknown error)
This error can be related to a known NTBackup issue described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;815140
Other possible resolutions
You can also try suspending any virus scan or other security software while the backup is running and avoid the use of CPU intensive programs such as MP3 players, Media players, data compression etc. You can suspend other programs by adding commands to the scripting section in the BackupAssist job edit area.
It's also been confirmed that writing to a backup destination which is already NTFS encrypted can also generate this error. To resolve this disable compression on the destination before you perform your backup.
| Last updated | Created | Further assistance |
|---|---|---|
| 09th Dec 2009 | 16th Mar 2007 | BackupAssist Support page |