Xopero ONE supports multiple repository selection methods that allow administrators to define the scope of backup and recovery operations according to organizational requirements. Repositories can be selected manually, automatically, or included and excluded based on configurable rules and filters.

Selecting data to protect

When creating a backup plan, one of the steps is to specify which repositories you want to protect. Xopero ONE offers several methods for selecting repositories:

1. Protect all: this option ensures that all existing repositories and projects, as well as any newly created ones, are automatically included in the backup plan without requiring manual updates.

2. Select projects: using checkboxes, you can choose specific projects to protect.

3. Select repositories: using checkboxes, you can choose specific repositories to protect.

1. Exclude repositories: using checkboxes, you can exclude specific repositories, allowing the plan to cover all other repositories by default.

2. Set rules: this option lets you define criteria to include repositories and projects based on attributes such as their names or associated topics, ensuring that repositories meeting these conditions are automatically protected.

Xopero ONE supports backup and recovery of Git Large File Storage (LFS) content for DevOps organizations, ensuring that repositories configured with Git LFS are protected together with their associated large binary objects. During restore operations, both standard Git data and LFS objects are recovered to preserve repository integrity and maintain consistency across supported DevOps platforms.

Xopero ONE supports the backup and recovery of LFS objects across all supported DevOps platforms.

While you can choose whether to include LFS metadata during the recovery process, please note that LFS must be restored alongside its parent repository; it cannot be recovered as a standalone item.

Rate limits enhance security by preventing an overwhelming number of requests that could disrupt, block, or destabilize the application's functionality—the system enforces these limits for stability. For more information, visit .

In Azure DevOps Server (on-premises), API limits are flexible and depend on server resources and configuration. Unlike the cloud version, there are no fixed, global request limits—administrators set performance parameters and limits tailored to the organization's specific needs.

Rate limits are enforced for security and stability— excessive requests may block access or disrupt the application’s operation. For detailed information, refer to the .

Xopero ONE provides selection rules, allowing administrators to determine which repositories and projects are included or excluded from backup and recovery tasks. Rules can be based on names, owners, creation dates, branches, or specific patterns, offering granular control over the backup scope and ensuring that only relevant repositories and projects are processed.

Selection rules and rule patterns

Below are the selection rules and rule patterns you can use in Xopero ONE to select repositories and projects for inclusion in backup jobs within your DevOps organization.

Azure DevOps & Bitbucket

1. Repository name — you can use the full or partial name of a repository. Wildcard characters can be used at the end of the rule to match repository names:

   1. * matches zero or more characters

   2. ? matches exactly one character

2. Project name: protects all repositories within the specified project.

1. Repository name — you can use the full or partial name of a repository. Wildcard characters can be used at the end of the rule to match repository names:

   1. * matches zero or more characters

   2. ? matches exactly one character

1. Repository name — you can use the full or partial name of a repository. Wildcard characters can be used at the end of the rule to match repository names:

   1. * matches zero or more characters

   2. ? matches exactly one character

The following are examples of rule patterns, along with brief explanations:

• Pattern: yourorganization/*

  • This will match all repositories in the organization named yourorganization.

• Pattern: yourorganization/n??

All selection rules can use regular expression patterns (regex).

Regular expressions let you create flexible and adaptable rules that align with your organization's naming conventions. This approach allows precise targeting and automation based on consistent patterns in repository or project names.

The following are illustrative examples of how these rules can be applied, although the available configurations extend well beyond these cases:

• Pattern: yourorganization/repo[0-9]+

  • This will match repositories such as repo1, repo12, repo123, and so on.

Adding an Azure DevOps Server to Xopero ONE connects your projects and repositories to the platform, enabling seamless backup management and secure data protection.

Using a Personal Access Token (PAT)

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.

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.

Creating an Azure DevOps (or DevOps Server) backup plan ensures your projects and data are securely protected and easily restorable.

Backup plan setup

Restoring multiple Azure DevOps projects enables organizations to quickly recover projects, repositories, and source code at scale, ensuring consistent and reliable restoration across the development environment.

Recovery process

The below steps demonstrate how to restore multiple Azure DevOps projects at once using Xopero ONE Management Service.

To protect a Bitbucket environment with Xopero ONE, the account or token used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup. The specific permission scopes vary depending on the chosen authorization method.

OAuth permissions

When integrating Bitbucket using the OAuth authentication method, Xopero ONE requires the following permissions to securely access and protect your repository data:

• Account

  • Read and modify account information.

• Issues

  • Read and modify repositories' issues.

• Pipelines

  • Access repositories' build pipelines and configure their variables.

• Project settings

  • Read and modify workspace's project settings.

  • Read and transfer repositories within workspace's projects.

• Repositories & pull requests

  • Administer repositories.

  • Delete repositories.

  • Read and modify repositories and their pull requests.

• Manage runners

  • Access and edit workspaces and repositories' runners.

• Snippets

  • Read and modify code snippets.

• Team membership

  • Read and modify team membership details.

• Workspaces

  • Access your workspaces for authentication.

  • Access and edit your workspaces and repositories' test.

• Webhooks

  • Read and modify repositories' webhooks.

• Wikis

  • Read and modify repositories' wikis.

Every API token created for Bitbucket integration with Xopero ONE requires specific permission scopes to restrict data access and define the exact operations the token can execute.

To ensure successful backup and recovery tasks, API token must be provisioned with the below required permissions.

• read:webhook:bitbucket (hooks)

• read:user:bitbucket (required to link the organization)

• read:repository:bitbucket (repositories, downloads, synchronization)

• read:pullrequest:bitbucket (pull requests)

• read:pipeline:bitbucket (schedules)

• read:pullrequest:bitbucket (pull requests)

• read:webhook:bitbucket (hooks)

• read:issue:bitbucket (issues)

Recovering an organization wiki restores lost or overwritten documentation, enabling projects to quickly regain access to their knowledge base without affecting other repository or project metadata.

Recovery process for Bitbucket, GitHub, and GitLab

The following steps demonstrate how to quickly recover your wiki using Xopero ONE Management Service.

The following steps demonstrate how to quickly recover your Azure DevOps project wiki using Xopero ONE Management Service.

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.

Xopero ONE allows organizations to restore individual Azure DevOps repositories along with their associated metadata. The process ensures repository integrity and consistency while minimizing impact on other projects, supporting efficient disaster recovery, migration, and point-in-time restore operations.

The following steps demonstrate how to quickly restore a single Azure DevOps repository using Xopero ONE Management Service.

Recovering multiple Azure DevOps repositories simultaneously enables organizations to quickly restore only the selected repositories, ensuring consistent and reliable recovery across the development environment.

The following steps demonstrate how to restore multiple Azure DevOps repositories at once using Xopero ONE Management Service.

Single repository recovery for Bitbucket enables restoration of an individual repository together with its complete Git history, branches, tags, and associated metadata, without impacting other projects or repositories within the workspace.

The below steps demonstrate how to quickly restore a single Bitbucket repository using Xopero ONE Management Service.

Xopero ONE enables multiple Bitbucket repositories recovery, allowing administrators to restore several repositories simultaneously within a selected organization or project scope. The process preserves Git history, branches, tags, and supported metadata, ensuring data integrity and consistency across the restored resources.

The below steps demonstrate how to restore multiple Bitbucket repositories at once using Xopero ONE Management Service.

Xopero ONE enables single project recovery for Azure DevOps, allowing organizations to restore individual projects along with their selected metadata, ensuring data integrity and consistency while minimizing disruption to other projects and repositories.

Recovery process

The below steps demonstrate how to quickly restore a single Azure DevOps project using Xopero ONE Management Service.

The account used for integration must have an appropriate access level assigned within Azure DevOps:

• Basic.

• Visual Studio Subscriber — professional or enterprise tier.

Bitbucket protected resources define which parts of your environment Xopero ONE can access, secure, and restore.

The following list includes all Bitbucket resources covered by backup.

Using username and password

Xopero ONE enables cross-recovery across DevOps ecosystems by letting organizations restore repositories and associated metadata between different hosting providers such as GitHub, GitLab, Bitbucket and Azure DevOps. Recovered content covers repositories and many forms of metadata, including pull requests, wikis, issues and other repository artifacts where supported by the source and target platforms.

The following tables outline which resources and metadata can be cross-restored between platforms.