Process overview

Learn more about the backup process for Azure DevOps.

The Azure DevOps & DevOps Server backup process in Xopero ONE securely connects to your DevOps environment, captures repositories, projects and related metadata, and stores verified backup copies that can be restored when needed.

---

General information

Xopero ONE is designed to protect DevOps ecosystems, including Azure DevOps.

To ensure your entire Azure DevOps environment is reliably backed up, make sure to include all repositories along with their related metadata — the best practice is to create a backup plan for critical repositories and metadata that change daily (or even more frequently), for example, using the recommended Grandfather-Father-Son (GFS) rotation scheme.

Additionally, create a separate backup plan for unused repositories that you need to keep for future reference. This type of backup primarily serves Azure DevOps archival purposes, and with unlimited retention, you can store your copies for as long as needed — even indefinitely.

You can also delete repositories from your Azure DevOps account while keeping a copy in storage, which helps bypass Azure DevOps limits.

---

Backup type

Incremental and differential backups help save storage space. In Xopero ONE you can define different retention and performance settings for each type of backup (full, incremental, and differential). For example, our software allows you to include only the blocks of Azure DevOps data that have changed since the last backup, reducing storage usage, speeding up the process, and limiting bandwidth.

---

Adding multiple storage instances

Use different types of storage to replicate backups, minimize the risk of outages or disasters, and comply with the 3-2-1 backup rule (which means having at least three copies of your data on two different storage types, with at least one copy stored in the cloud).

Xopero ONE is a multi-storage system that allows you to store your data:

• In the cloud (Xopero Cloud Storage, AWS S3, Wasabi Cloud, Backblaze B2, Google Cloud Storage, Azure Blob Storage, or any S3-compatible public cloud).

• Locally (NFS, CIFS, SMB network shares, or local disk resources).

• In a hybrid or multi-cloud environment.