Auto-Update Process

Backblaze automatically updates Computer Backup Clients when a major release becomes available. A major release means a change in the second or third version number (for example, from 9.2.0 → 9.2.1), but not the minor build number. The goal is to bring all customers to the latest stable version to ensure security, performance, and feature consistency.

Updates are version-based, not time-based. Auto-updates are controlled centrally and enabled after a release has passed stability and telemetry thresholds. The typical rollout duration is about one month from start to full deployment.

Customers do not need to take action unless:

• They’ve blocked auto-updates, or

• They’re running a very old version that cannot update automatically (manual reinstall may be required).

Auto-Update Rollout Process

Updates are released gradually, starting with a small test cluster and then slowly increasing, in a controlled manner, the number of Backup Clients receiving the new build. This incremental rollout ensures that any unforeseen issues can be identified early before reaching the majority of customers.

Updates can also be modified, paused, or canceled off-schedule if needed. Update ramp-ups are more conservative and progressive, ensuring smoother customer experience. Development and testing procedures are in place to prevent repeat issues.