Datto incident
Endpoint Backup v2 - A Subset of Endpoint Backup v2 Assets May Experience Backup Failures
Datto experienced a major incident on June 12, 2026 affecting Backup, lasting 2d 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 12, 2026, 07:57 PM UTC
We are aware of a problem where a subset of Endpoint Backup v2 assets can experience a backup failure due to error "system.ntfs_reparse_data: invalid argument". The Kaseya R&D Team has identified the issue and is working towards a resolution. In the meantime our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- monitoring Jun 15, 2026, 01:29 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 15, 2026, 05:06 PM UTC
This incident has been resolved.
- postmortem Jul 21, 2026, 06:47 PM UTC
**Endpoint Backup v2 - Subset of Endpoint Backup v2 Assets Experienced Backup Failures Due to a "system.ntfs\_reparse\_data: invalid argument" error –2026-06-12** **Summary:** Between **2026-06-12 01:00 PM UTC** and **2026-06-15 08:00 PM UTC**, Endpoint Backup v2 customers experienced an issue where a subset of Endpoint Backup v2 assets experienced failed backups due to error "system.ntfs\_reparse\_data: invalid argument". **Root Cause:** After the 1.14 agent release, we identified a compatibility issue involving certain third-party components that resulted in backup failures for a subset of customers. We quickly applied a temporary workaround, released a permanent fix, and then removed the workaround once the fix was in place. The issue has been resolved, and backup operations are functioning normally. **Incident Timeline:** * Identified: **2026-06-12 01:00 PM UTC** * Public Notification: **2026-06-12 08:57 PM UTC** * Resolved: **2026-06-15 08:00 PM UTC** **Preventative Measures:** To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. * To prevent similar issues in the future, we have implemented a whitelist-based approval process for symlink support, providing additional controls and reducing the likelihood of recurrence.