Skip to content
Download a free 30-day trial

BA753: File Protection destination drive could not be written

Error code Product Applies to
BA753 BackupAssist For BackupAssist 15.0.5 or later.

Description

During a File Protection backup, BackupAssist writes each source file to the configured backup destination. The destination may be a local drive, USB drive, network share, or NAS device.

BA753 is recorded when one or more destination write operations failed and the job did not recover - no files were successfully written to the destination after the first failure. This indicates a storage-layer failure on the backup destination rather than a problem with the source data.

Common causes:

  • Bad sectors on the destination drive - write operations fail at a specific location on the disk.
  • The destination drive was physically disconnected or lost power mid-backup.
  • The destination drive is full or has insufficient free space.
  • A NAS or network destination became unreachable during the backup.

Resolution

  1. Open Windows Event Viewer on the machine where the backup ran and check the System log for disk error events around the backup start time.
  2. Run a drive health check using "chkdsk /r" from an elevated Command Prompt, or use a vendor diagnostic utility for the destination drive.
  3. If the drive is failing, replace it and reconfigure the backup job to point to the new destination.
  4. Re-run the File Protection backup to confirm it completes without BA753.

Resolution 2 - Check the physical connection (external drives)

If the destination drive is external (USB, eSATA):

  1. Check the cable and port. Try a different USB port or cable.
  2. Connect the drive directly to the machine rather than through a hub.
  3. Re-run the backup.

Resolution 3 - Check available space on the destination

  1. Open File Explorer and check the free space on the backup destination drive.
  2. If the destination is nearly full, delete old backup sets or configure a larger destination.
  3. Re-run the backup.

Resolution 4 - Identify affected files

  1. Open BackupAssist. The job list is shown in the Overview.
  2. Locate the failed backup run and open its report.
  3. Expand the File Replication section and review the list of destination write errors.
  4. Arrange an alternative backup for any critical files that were not protected.

Note on the backup report

When BA753 is recorded, the backup report displays: One or more files could not be written to the destination and the job did not recover. Check the File Replication section for details. The File Replication section contains the individual file entries showing the error code and destination path for each file that could not be written.

Last updated Created Further assistance
7th Aug 2026 7th Aug 2026 BackupAssist Support page
Download a free 30-day trial