October 11
August 7
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.
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 .
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.
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.
In Xopero ONE version 1.8.5, we added support for:
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.
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.
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.
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.
Version 1.8.5 introduces improved data processing for used storage space in AWS S3 and S3-compatible data stores.
In this release, we optimized processes that consumed a large amount of RAM.
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.
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.
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.
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.
This bug has been fixed. Calendar statistics are now displayed correctly, regardless of the Xopero Management Service operation model.
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.
The bug occurred when a user ran a Microsoft 365 backup that included account contacts. The error has been identified and fixed.
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.
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.
A bug that prevented child issues from being restored individually from team-managed (next-gen) projects has been fixed.
We have completely redesigned the onboarding process for new users. When logging in for the first time, the user is directed to a new screen that presents all available resources that can be secured with Xopero. By default, a new user can connect a service with Xopero ONE using a simple three-step process. However, if a SaaS organization requires authorization via login, token, or GitHub App, the previous advanced mode is still available.
The upper blue bar (which contains the context menu for the currently visible subpage) has also been updated. It now allows quick configuration of a new backup plan and adding new services to protect. The language setting has been moved to the User actions, and an easy option to upgrade or purchase licenses is now available.
To enhance the security of user data, encryption is now enabled by default for every new backup plan. A default encryption key is generated for this purpose, which can be viewed only once at the time of creation.
For each supported ecosystem and service, Xopero ONE offers a dedicated type of backup plan. Starting from version 1.8.0, users can choose between backup plans for physical devices, VMware, or Hyper-V, as well as SaaS services such as Microsoft 365, GitHub, Bitbucket, GitLab, and Jira. Each plan can then be configured according to the security policies of the organization.
With this release, we address issues related to insufficient RAM allocation. When there is not enough RAM to perform an operation, the service will automatically request additional resources. In the initial phase, this mechanism operates in manual mode: the service sends the request automatically, but the resources are assigned only after user approval. Additionally, we have introduced optimizations that improve the release of used RAM, reducing overall consumption. This enhancement benefits not only SaaS users but also on-premise and Xopero Unified Protection users.
Xopero ONE users can now set the time zone within the backup plan schedule, ensuring that all future tasks are launched according to the selected time zone. This improvement eliminates the need to manually adjust the time zone during winter or summer time changes.
In this release, we have improved the process of restoring deduplicated data from cloud storages. Restoring file-level and Microsoft 365 backup copies will now be significantly faster.
We have improved handling of symbolic links by adding a setting that allows users to choose whether:
The agent should follow symbolic links, backing up the files and directories they point to.
The agent should not follow symbolic links, backing up only the link itself without its content.
The config.json file in the agent installation directory allows users to store additional configuration settings. Previously, this file was overwritten during each update, requiring users to re-enter their configuration changes. Starting with this release, changes in the config.json file will be preserved during updates.
Xopero ONE now offers a new type of Slack notification: the SLA report is ready for download.
Starting from version 1.8.0, all system passwords are hidden and no longer visible in the app UI. This proactive measure prevents users from deleting or modifying system passwords.
For user-created data storages, the correct default worker for browsing the storage is now automatically selected, but can be manually changed in the settings (changing the worker in settings now works correctly).
Additionally, an error notification is displayed if a user attempts to browse a storage using a worker they do not have access to. Previously, the absence of such a notification could mislead users into thinking the storage was empty.
We have improved the performance of Hyper-V virtual machines running in instant restore mode from cloud storages by implementing a new cache.
The Hyper-V license also allows creating copies directly from the host where virtual machines are running (users can back up files as well as disk images). Previously, tasks completed by this type of host were not reflected in the SLA section of the dashboard.
Previously, if a Hyper-V virtual machine disk name contained a # character, the backup plan would fail, and the data could not be restored. This bug has been fixed in this release.
Previously, if a user had added multiple storages to the service and then added Hyper-V, it was impossible to run the default Hyper-V backup plan. This issue has been resolved: the user now selects the storage where the backup copies should be saved. Before the default plan starts, the plan editing screen is displayed at the storage selection stage.
We have revised how backup plan details are displayed in the VM dashboard and improved the process of adding a Hyper-V cluster.
Previously, Hyper-V virtual machines with a 5.0 configuration would fail during backup. Starting from version 1.8.0, 5.0 configuration is supported, allowing these machines to be backed up correctly.
Due to a change in the data format returned by the Microsoft 365 service, restoring a mailbox to PST format had stopped working. This bug has been fixed, and mailbox restoration to the user's computer is now possible again.
We have fixed an issue with VM list synchronization that occurred after combining VMware datastores into a cluster.