BA1119: Cannot write to the media - possible hardware failure¶
| Error code | Product | Applies to |
|---|---|---|
| BA1119 | BackupAssist | BackupAssist Version 4 |
Description¶
This error may appear as one of three possible conditions:
- Error: The device reported an error on a request to write data to media.
- Error reported: Unknown error. Indicates a scheduling conflict
- Error reported: Bad data. Indicates a hardware problem
Resolution¶
In the details of this error you should be able to find one of the two messages: Error reported: Unknown error, or Error reported: Bad data. The resolutions for these two error messages are different.
Resolution 1. Bad data: Tape hardware issues
There are several possible causes for this error:
Contaminated read/write heads of the tape device. Running 3-4 consecutive cleaning cycles will usually resolve this problem.
Bad media; try a newer, less used tape.
Tape head alignment problems; replace or service the tape device.
SCSI transfer rate to the tape device is too fast; use the manufacturer's SCSI setup program to lower the transfer rate.
Sync negotiation problems; disable the sync negotiation to the tape device in the SCSI setup program.
Faulty SCSI component; check/replace the SCSI cable or terminator.
Controller conflicts; isolate the tape drive on its own controller card.
Resolution 2. Bad data: NAS hardware issues
This error can occur if the network is running slowly or becomes disconnected. Check that the backup machine can still access the network.
If you continue to receive this error try using the option to Keep local copies of your backups. That will force BackupAssist to backup to a local drive, then copy the backup from the local drive to your NAS destination. This can often improve the success rate of your backups.
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. Bad data: other destinations
This error will occur if BackupAssist cannot communicate with your destination hardware for several seconds. If, for example, a removable hard drive has become unplugged, or a cartridge destination is responding very slowly. Make sure that your destination is accessible and connected throughout the backup process.
Resolution 4. Unknown error: Scheduling issues
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 5. 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.
| Last updated | Created | Further assistance |
|---|---|---|
| 15th May 2017 | 16th Mar 2007 | BackupAssist Support page |