Xopero ONE 1.8.5
🆕 NEW FEATURES
Azure DevOps support
With the 1.8.5 release, Xopero ONE supports backing up Azure DevOps data, making our solution compatible with all leading Git service providers. Like GitHub, GitLab, and Bitbucket backups, Xopero ONE allows cross-restore to and from Azure DevOps. Users can back up both Azure DevOps (SaaS) and Azure DevOps Server (on-premise) organizations.
Azure DevOps backup
Users can back up both Azure DevOps projects and repositories. During plan configuration, users can choose one of four resource types to protect:
Whole organization, which is the recommended option.
Projects, with the ability to select individual repositories within each project.
Repositories.
Specific resources based on rules, such as repository name (slug) or project name (slug).
Users can also define which metadata to include in the backup. The option to include or exclude individual metadata depends on the selected resource type. The full list of supported metadata is available here.
Azure DevOps restore
Backed-up data can be restored to the same or a new Azure DevOps organization. Using cross-restore between different Git service providers, Xopero ONE allows Azure DevOps data to be restored to GitHub, Bitbucket, or GitLab accounts. This ensures uninterrupted workflow for Azure DevOps operations, even if Microsoft’s service is unavailable.
The metadata available for restore may vary depending on the selected Git service provider. When restoring projects within Azure DevOps, both the project metadata (e.g., work items) and the contained repositories are restored. During cross-restore to another Git hosting provider, only repositories and their metadata are restored, as there is no equivalent of Azure DevOps projects in these services.
Xopero ONE backup for Azure DevOps is licensed per number of repositories and sold in packages.
Excluding selected repositories from the backup plan
In response to customer needs, version 1.8.5 introduces a new mode for selecting repositories to back up within GitHub, GitLab, and Bitbucket backup plans. When selecting an organization to back up, users can now exclude specific repositories — by default, all repositories are selected, and users can deselect the repositories they want to exclude. A backup plan configured this way will protect all repositories in the organization except the excluded ones. Repositories added in the future will also be included in the plan.
New GitHub metadata support
In Xopero ONE version 1.8.5, we added support for:
Organization dashboard 2.0
Organization dashboards have been redesigned for improved clarity. The Plan section is now easier to read, and screen resolution support has been optimized. This update applies to devices, Microsoft 365, Hyper-V, VMware, and all Git and Jira organizations.
🔨 IMPROVEMENTS
S3 buffer size configured within the backup plan
From now on, the buffer size used for communication with AWS S3 data stores can be configured during backup plan setup and in edit mode for file-level, image-level, Hyper-V, VMware, and Microsoft 365 backup plans.
Improved task package queuing
Conflicting task types, such as deleting and restoring data from the same datastore, are now displayed as queued tasks in the Tasks tab (In progress) and are always executed in descending order. Previously, some tasks were queued in the background and invisible to users. This issue has now been resolved.
Webhook URIs validation improved (Management Console)
Characters such as single quotes, brackets, exclamation marks, and asterisks are not supported in webhook addresses, as they cause validation errors. Previously, using these characters did not display an appropriate error message — this issue has now been fixed.
AWS S3 storage usage data
Version 1.8.5 introduces improved data processing for used storage space in AWS S3 and S3-compatible data stores.
RAM usage optimization
In this release, we optimized processes that consumed a large amount of RAM.
Editable organization name
By default, Xopero ONE uses and displays the original organization name. Starting from version 1.8.5, users can edit this name as needed. This change applies to all types of Git organizations: GitHub, GitLab, Bitbucket, and Azure DevOps.
Unified view of repository names
Starting from version 1.8.5, the repository name field displays the actual repository name instead of the slug (path). For users who found the old feature useful, a new slug field has been added to the repository table. This field is also supported by the filtering and search functions. To enable it, use the table configuration icon.
Branch protection rules with extended support
Previously, it was not possible to back up branch protection rules that referenced private GitHub App applications when using the GitHub authorization method. Version 1.8.5 introduces a mechanism that detects such cases and uses a personal access token to back up these settings instead.
🐛 BUGFIXES
Incorrectly displayed number of tasks in progress
Previously, when running more than 10 tasks, the panel displayed a maximum value of 10, even if more tasks were actually in progress. This issue has been fixed. The value shown in the menu now reflects the actual number of active tasks in the Tasks section.
Task statistics in the calendar of the resource dashboard (SaaS services)
This bug has been fixed. Calendar statistics are now displayed correctly, regardless of the Xopero Management Service operation model.
Incorrect sorting by columns in the device view
We found that sorting by the columns IP address, Last copy, or Last successful copy in the device list was not working correctly. This bug has been fixed, and sorting now functions properly.
Microsoft 365 backup ended with "Data supplier error"
The bug occurred when a user ran a Microsoft 365 backup that included account contacts. The error has been identified and fixed.
No snapshot cleanup after failed Hyper-V backup
In some cases, if a backup failed, the cleanup operation did not start, and the snapshot from that backup was not removed. As a result, these snapshots occupied hypervisor storage space.
Restoring files with permissions ends with an ACL warning
The error occurred only when restoring data from a file-level backup in very specific cases. As a result, users were unable to restore ACL permissions along with the data. This bug has been fixed in version 1.8.5, and permissions are now restored correctly.
Child-issues restore in Jira team-managed projects
A bug that prevented child issues from being restored individually from team-managed (next-gen) projects has been fixed.
Last updated