Index of backup and restore error codes
Last updated:Dec 4, 2024
Index of backup and restore error codes
Details
The table below lists some of the common error codes you may encounter during backups or restorations using the following services:
- ActiveProtect Manager
- Active Backup for Business
Windows PC or physical servers
| Error Code | Description |
|---|---|
| 0x80042301 |
Failed to take snapshots for the specific volume. (Learn more) |
| 0x80042302 | |
| 0x80042306 |
An error occurred when certain Volume Shadow Copy Service providers on the PC created snapshots. (Learn more) |
| 0x8004230F | |
| 0x80042308 | The agent cannot find the snapshot created during a backup task. (Learn more) |
| 0x8004230C | The device fails to take a snapshot for a volume. (Learn more) |
| 0x80042313 | Excessive activities on the volume might have caused a failure to take snapshots for the volume. (Learn more) |
| 0x80042316 | Other applications or systems are creating VSS snapshots. (Learn more) |
| 1117 | Access to snapshots failed due to an I/O device error. (Learn more) |
| 2 | The system cannot find the snapshot required for backup or can no longer access the snapshot. (Learn more) |
| 1 |
Insufficient shadow storage reserved for use by third-party software. (Learn more) |
| 21 | |
| 0x8004231f | |
| 23 | The disk selected for backup has bad sectors. (Learn more) |
| 27 | An error occurs when a volume shadow is being accessed. (Learn more) |
| 5 | The agent cannot access a snapshot. (Learn more) |
macOS devices
| Error Code | Description |
|---|---|
| -1 |
Failed to execute Apple Software Restore (asr) on the volume. (Learn more) |
| -2 | |
| -3 | |
| -4 | An I/O error occurred on the internal drive. Run a drive health check and repair drive errors (e.g., with the First Aid feature). If the problem persists, contact Apple for support. |
| 1C | Unable to take a snapshot because the data volume does not have enough free space. Release some space and try again. |
| 1E | Unable to take the snapshot for the mounted volume because it is in read-only mode. Ensure you have permission to take the snapshot in the mount option. |
| 10 | The device is busy. Try again later. |
| 28 | Unable to take a snapshot because the data volume doesn't have enough free space. Free up some volume space and try again. |
| 49244 | Cannot run Apple Software Restore (asr) to back up data on a specific data volume because APFS or data are corrupted. (Learn more) |
Linux physical servers
| Error Code | Description |
|---|---|
| 0xffffffffffffffa1 | The current kernel version is not supported and requires to be upgraded to 2.6.23 or above. You can check your current version by entering the "uname -a" command. |
| 0xffffffffffffffb3 | The system is unable to load the driver. Enter the "sudo modprobe synosnap" command to load the driver and perform the backup task again. |
| 0xffffffffffffffe4 | Insufficient storage space for taking snapshots for the specific volume. Enter the "df" command to check whether the available storage space on the volume is more than 10%. If not, free up space and perform the backup task again. |
| 0xffffffffffffffe5 | During backup, the changed block size exceeds 10% of the volume capacity. Retry the backup and avoid updating the system or actively changing data during the process. |
| 0xfffffffffffffff3 | Unable to take the snapshot for the mounted volume because it is in read-only mode. Ensure you have permission to take the snapshot in the mount option. |
| 0xfffffffffffffff4 | The Linux system is out of memory. Enter the "htop" command to monitor memory usage. You can close other memory-consuming applications and perform the backup task again. |
| 0xfffffffffffffffe | The snapshot driver is not installed correctly. Make sure your Linux distribution and kernel version are supported by checking the requirements and limitations for ActiveProtect Manager or Active Backup for Business. To check the kernel version, run the "uname -a" command. |
Recovery media creators
| Error Code | Description |
|---|---|
| 0x241 |
|
| 0x3 | Windows Preinstallation Environment (Windows PE) is missing, causing the recovery media creator to fail. (Learn more) |
| 0x80070015 | USB external device can't be accessed after the system formatted it. (Learn more) |
| 0xC1420114 | The mounted folder was not empty before creating USB recovery media. (Learn more) |
| 0xC1420117 | Some applications still have files open within the mount directory. Thus, the directory could not be unmounted. (Learn more) |
| 0xC142011D | Incorrect configuration settings in Windows Deployment Image Servicing and Management (DISM) prevented your recovery media from unmounting. (Learn more) |
| 0xC1420127 | The mount folder is already a mount point for other Windows Imaging Format (.wim) images. The previous WIM has not been unmounted. (Learn more) |
Recovery tools
| Error Code | Description |
|---|---|
| 0x45D | An I/O error occurs during the restoration process. (Learn more) |