Acronis telemetry of ~960 million backup job executions in H2 2025 reveals high failure concentrations during off-hours—especially Friday 01:00 and 02:00—with full backups at 02:00 failing at 21.61%. The report quantifies scheduling peaks (23:00 avg 185,693 jobs/day), identifies optimal hours by backup type (full best at 06:00, custom best at 14:00), and prescribes scheduling and monitoring changes to cut failure risk and business impact. #Acronis #SpaceQuotaReachedHard
Keypoints
- Off-hours blind spot: In data center-local time the 02:00–05:00 window averages a 7.01% failure rate, and Friday 01:00 is the single worst hour-day cell at 11.12%.
- Full backups are highly sensitive to schedule: full backups at 02:00 fail at 21.61%, while moving them to 06:00 reduces failure to 3.97% (a 5.4× improvement).
- Schedule concentration: 23:00 local time is the peak scheduling hour (avg 185,693 jobs/day, median 196,084) with a peak-to-valley ratio of 2.4× vs. 05:00.
- Backup-type matters: different backup schemes have distinct optimal hours (custom policies at 14:00 = 2.61% failure; always_incremental best at 16:00 = 5.13%).
- Error profile: Off-hours failures are dominated by customer-side errors such as SpaceQuotaReachedHard and MemoErrorVssWriterFail, which require human intervention to resolve.
- Business impact: Undetected weekend failures (e.g., Friday 01:00) create extended RPO exposure and material downtime costs measured in thousands to millions of dollars across tenants.
- Practical playbook: Spread schedules, adopt backup-type-aware timing (full at 06:00 or 13:00–16:00, incremental at 16:00, custom at 14:00), prioritize business-hours monitoring, and treat Friday as highest-risk day.
MITRE Techniques
- [None ] No MITRE ATT&CK techniques mentioned – ‘No ATT&CK techniques referenced in the article.’
Indicators of Compromise
- [Error identifier ] off-hours dominant failure types – SpaceQuotaReachedHard, MemoErrorVssWriterFail
- [Backup scheme tags ] used to classify job types and failure profiles – always_full, always_incremental, custom_policies