acronis "backup failed error code 0x01350016"

TL;DR

Open the failed Acronis activity and read the sub-error under code 0x01350016 first, because that code is a wrapper and the real cause sits in the detail line below it. Check VSS writers, free space and archive access, fix that one cause, validate the newest archive, then rerun the plan. Do not reinstall the agent until the detail names an agent component.

acronis "backup failed error code 0x01350016"

Use this when

• An Acronis Cyber Protect or Cyber Backup plan fails and the console shows error code 0x01350016.
• The same plan worked before and now fails at snapshot, write or validation stage.
• You need the underlying module error, not just the top level activity summary.

Not for this skill when

• The plan never starts because the machine is offline or the agent is unregistered. Register the machine first.
• A different Acronis code appears with a clear disk or network message and no 0x01350016 wrapper.
• The archive itself opens but a restored machine will not boot. Use a bare metal recovery skill.

Steps

1. In the Acronis console open Activities, open the failed run, and expand the full error detail and any additional info lines under 0x01350016. Note the named stage, module and the Windows or VSS code if one is listed, because the fix branch depends entirely on that line. Verify: the detail names a concrete stage such as snapshot creation, archive write or validation instead of only the wrapper code
2. On the protected machine check the Acronis Managed Machine Service and the scheduler service are running, then restart them once if the detail points at a lost connection to the agent. Confirm the machine shows online in the console before rerunning anything. Verify: the machine reports online and a manual plan start reaches the snapshot stage
3. If the detail mentions VSS, run vssadmin list writers from an elevated prompt and look for writers in a failed or timed out state, then reboot or restart the owning service for an unstable writer. Check the volume shadow copy storage has room for the snapshot, especially on small system volumes. Verify: vssadmin list writers shows all writers stable with no errors and shadow storage is not capped below the changed data size
4. Check the backup destination for free space, share reachability and the stored access entry for that location. Browse to the location from the protected machine using the same account the plan uses, open an existing archive folder, and confirm a small test file can be created and deleted there. Verify: the plan account can read an existing archive and write to the destination, and free space exceeds the expected incremental size with margin
5. Run validation on the newest successful archive from the console vault view. If validation fails on one archive while older archives pass, isolate that archive, keep it for support, and start a new full backup to a clean archive name rather than continuing the damaged chain. Verify: validation completes clean on the newest good archive or a fresh full backup completes and validates
6. Rerun the protection plan manually outside the normal schedule and watch it pass the stage named in step 1. If it fails again with a different sub-error, treat that as new evidence and do not repeat the first fix. Verify: the manual run finishes successfully, the archive timestamp updates, and the next scheduled run also succeeds

Why it happens

Code 0x01350016 is reported by operators as a generic operation failure wrapper in Acronis activities. The job can fail at several unrelated layers: a VSS writer that will not freeze the application, a snapshot that runs out of shadow storage, a network location the plan account can no longer write to, an antivirus filter intercepting the archive format, or a damaged archive that only validation finds. The console summary collapses those into one code, which is why reinstalling or blindly retrying so often wastes a backup window. Reading the expanded detail, testing the exact stage, and validating the last good archive separates a transient writer fault from real archive damage.

Variants and edge cases

Antivirus and endpoint protection deserve a specific check on Windows machines. Acronis tibx archives and snapshot activity are sometimes scanned or blocked, producing intermittent failures that vanish on a manual daytime run when scanning load differs. Add the vendor recommended exclusions for the Acronis processes and archive location only after the detail supports it, then prove the change with two consecutive scheduled runs, not one manual success.

acronis backup plan failed 0x01350016 module error

Use this phrasing when the activity detail also shows a module number. The module and message line, not the wrapper code, tell you whether the fault is in snapshot handling, archive storage or the agent service itself.

acronis cyber protect backup failed with error after working for months

The regression phrasing. Prior success shifts suspicion to change: a Windows update that destabilised a VSS writer, a filled destination, rotated share credentials in the plan, or new endpoint protection rules.

acronis validation fails on archive created after 0x01350016

Use when the backup appears to finish but validation flags the result. Stop extending that chain, preserve the suspect archive for support, and seed a new full backup after the underlying stage fault is fixed.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstNJq77L9oT7u4sWYLOvE2w