This article contains information on how to set up Azure DevOps & DevOps Server backup plan.
Login to Xopero ONE Management Service, open the Plans > Backup tab and click the Add plan button in the top bar.
Select Azure DevOps from the list.
Select (or add) the Azure DevOps or DevOps Server environment you want to include in the backup process, and choose the repositories to back up.
Protect all — protects an entire Azure DevOps organization.
Select projects — allows you to protect selected Azure DevOps projects (including its metadata).
Select repositories — protects only
Specify a name for the backup plan.
Select the appropriate metadata that you want to back up. Here, you can also change the default worker, which is the device directly responsible for the backup process of your repositories.
Select one of the locations assigned to your Xopero ONE instance as storage.
Customize the scheduler and specify how long your data should be retained. If needed, adjust the advanced settings to suit your needs.
If necessary, adjust the advanced settings such as encryption, error handling, or bandwidth limits to fit your requirements.
Double-check your data and click Save to create the backup plan.
Set rules — lets you set rules for Xopero ONE to automatically select resources to protect.
Learn more about the backup process for Azure DevOps.
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.
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.
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:
Overview of protected Azure DevOps and Azure DevOps Server resources, including projects, repositories, wikis, and metadata secured by backup.
Azure DevOps protected resources define which parts of the environment Xopero ONE can access, backup, and restore.
The following tables list all Azure DevOps and Azure DevOps Server resources covered by backup.
*The restored comment is attributed to the account performing the restore; content includes the original comment author information and the original creation date.
**Assignee and identity-type fields are not restored directly; instead, a comment is added identifying the original assignee and related values.
***A work item type consists of a name, description, color, icon, enabled/disabled status, and its internal configuration (layout and states).
*Configuration and definitions are restored; logs, run history, and artifacts are not. Only YAML pipelines that use Azure Repos are supported.
**Secret variables are not backed up due to an API limitation.
*Included in backup, but can be restored only to GitHub and GitLab.
**Test run history is backed up and restored. The run state (for example, in progress or needs investigation) is restored in a separate step after the run is created.
***Automated test settings (associated pipelines) are not restored due to current pipeline restore limitations.