Acronis Cyber Protect backup failed error code 0x0190000B quota exceeded

Not specified by the original author.

TL;DR

Error 0x0190000B means the backup plan's storage quota is exhausted: check the consumed quota in the management console by workload and storage location, then either raise the quota, free space by expiring old archives per retention, or move the workload to a location with headroom. New backups cannot start until space exists under the quota, so this is an entitlement and retention problem, not a job retry problem.

Acronis Cyber Protect backup failed "error code 0x0190000B quota exceeded"

Use this when

• The job or restore fails with this symptom: Acronis Cyber Protect backup failed with error code 0x0190000B quota exceeded.
• You are working on an Acronis Cyber Protect backup failing on quota and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A quota that looks sufficient in the console while a different storage location's sub-quota is exhausted, where the fix is the location's limit.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open the console's quota view and record usage and limit for the affected workload and storage location. Verify: the exhausted quota is identified precisely
2. Review retention on that location for archives that should have expired but did not. Verify: recoverable space is estimated
3. Raise the quota, expire archives per policy, or reassign the plan to a location with headroom. Verify: space exists under the applicable quota
4. Run the backup on demand and confirm it completes and the quota view reflects the new archive. Verify: backups resume under quota

Variant phrasings

acronis backup error code 0x0190000b quota exceeded

The verbatim phrasing.

acronis cyber protect quota exceeded backup failed fix

The fix phrasing.

acronis 0x0190000b storage quota retention location

The location phrasing.

Compatibility: Acronis Cyber Protect quotas and cloud storage entitlements

Why it happens

Acronis enforces quota at the plan's storage location before the job writes anything, so an exhausted quota fails every run identically. The console aggregates can hide which location's limit is binding, which is why the check is per workload and per location rather than account-wide.

Edge cases / pitfalls

• Quota freed by retention applies on the platform's schedule; a backup retried immediately can still fail until the sweep runs.
• Growth trends predict this error weeks ahead; a quota report belongs in the monthly backup review.

Provenance

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

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

Thread query: Acronis Cyber Protect backup failed "error code 0x0190000B quota exceeded"

TL;DR: Error 0x0190000B means the backup plan's storage quota is exhausted: check the consumed quota in the management console by workload and storage location, then either raise the quota, free space by expiring old archives per retention, or move the workload to a location with headroom. New backups cannot start until space exists under the quota, so this is an entitlement and retention problem, not a job retry problem.

Not specified by the original author.

TL;DR

Acronis backup failed with error is a banner over a specific module error in the activity details. Open the failed activity, read the module and error code lines, and fix that layer: VSS writers, plan credentials, destination space, or the agent service. The banner alone never tells you which, so always work from the detailed log entry.

acronis backup failed with error

Use this when

• An Acronis Cyber Protect plan shows backup failed with error.
• The activity list shows a red failed entry with a details link.
• The same machine backs up after a reboot but fails again days later.

Not for this skill when

• Veeam or Commvault shows a similar banner. Their logs and codes differ.
• The Acronis agent is offline entirely. That is a connectivity problem first.

Steps

1. Open the failed activity details and record the module, error code and the first cause line. Verify: the specific Acronis error is captured, not just the banner
2. If the code points at VSS, check writers on the machine with vssadmin list writers and restart failed writer services. Verify: writers return to stable
3. If the code points at access or credentials, re-enter the plan credentials and test the destination path from the agent machine. Verify: the agent can open the destination with plan rights
4. If the code points at space or write errors, check destination free space and storage health. Verify: space and write tests pass
5. Rerun the plan and confirm the activity completes with a success entry. Verify: the plan produces a new recovery point

Variant phrasings

acronis cyber protect backup failed error code

The error-code focused phrasing.

acronis backup plan failed details

The activity-log variant.

acronis agent backup error module

The module-code wording.

Compatibility: Acronis Cyber Protect 15 and Cyber Protect Cloud agents on Windows and Linux, with local, network and Acronis Cloud destinations.

Why it happens

Acronis wraps many subsystems under one plan result: snapshotting, source reading, compression, destination writing and cataloguing. The banner reports only that one subsystem returned an error, while the activity detail carries the module number that identifies it. Reading the detail first turns a vague failure into a short, known fix list.

Edge cases / pitfalls

• Recurring VSS module errors after Windows updates are common. Check writer state before reinstalling the agent.
• A plan edited to a new destination keeps old credentials in some tasks. Re-save every task in the plan.
• Agent service stopped by endpoint protection shows as backup errors, not offline, if the management server still has a recent heartbeat.

Provenance

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

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

Thread query: acronis backup failed with error

TL;DR: Acronis backup failed with error is a banner over a specific module error in the activity details. Open the failed activity, read the module and error code lines, and fix that layer: VSS writers, plan credentials, destination space, or the agent service. The banner alone never tells you which, so always work from the detailed log entry.

Not specified by the original author.

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

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

Thread query: 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.