BA754: File Protection backup completed with some files skipped¶
| Error code | Product | Applies to |
|---|---|---|
| BA754 | BackupAssist | For BackupAssist 15.0.5 or later. |
Description¶
During a File Protection backup, BackupAssist reads each selected file from the source and writes it to the backup destination. If an error occurs on one or more files but the job continues and subsequently backs up other files successfully, the job is considered to have recovered from the error.
BA754 is recorded when copy errors occurred during the backup but the job recovered - at least one file was successfully backed up after the last error. The affected files are listed in the File Replication section of the report. All other files in the job were backed up normally.
Common causes:
- An isolated bad sector on the source drive affecting a single file.
- A transient connection issue on a USB or network source that resolved itself.
- A file that was locked or in use by another application at the time of backup.
If errors occurred and the job did not recover - no files were successfully backed up after the first failure - BA752 (source read failure) or BA753 (destination write failure) is recorded instead of BA754.
Resolution¶
Resolution 1 - Identify and re-protect the affected files (recommended)¶
- Open BackupAssist. The job list is shown in the Overview.
- Locate the backup run that produced BA754 and open its report.
- Expand the File Replication section to see the list of files that could not be backed up and the error codes returned.
- Determine whether the affected files contain critical data that must be re-protected, and arrange an alternative backup if necessary.
Resolution 2 - Check for developing hardware issues¶
A single isolated file error may indicate early-stage drive deterioration. If BA754 appears repeatedly across multiple backup runs, investigate the source drive health before it escalates to BA752.
- Open Windows Event Viewer and check the System log for disk error events around the backup time.
- Run "chkdsk /r" on the source drive from an elevated Command Prompt to scan for bad sectors.
- If bad sectors are confirmed, back up all data from the drive and replace it.
Resolution 3 - Check for files locked by other applications¶
If the affected files are database files, virtual machine disks, or files held open by a running application, they may have been locked at backup time.
- Review the file names listed in the File Replication section to identify any application-owned files.
- Consider scheduling the File Protection job to run outside business hours when those applications are less likely to hold the files open.
- For application-consistent backups of VSS-aware applications (SQL Server, Exchange, Hyper-V), ensure the relevant VSS writer is selected in the job.
Note on the backup report¶
When BA754 is recorded, the backup report displays: Some files could not be backed up but the job continued. Check the File Replication section for details. The File Replication section contains the individual file entries for each file that was skipped, including the error code and file path. All other files in the job were backed up successfully.
| Last updated | Created | Further assistance |
|---|---|---|
| 7th Aug 2026 | 7th Aug 2026 | BackupAssist Support page |