Jira granular backup allows you to back up selected Jira spaces and specific elements within them, with the option to exclude particular issues using JQL, which streamlines the backup process and enhances flexibility in data protection. It works alongside disaster recovery backup, which is still available for Xopero ONE users.
Support for backing up and restoring a new type of Azure DevOps data: artifacts (including feeds and packages) has been added to Xopero ONE.
The protected data range for GitHub projects v2 has been extended to include backup and restore of draft issues, as well as additional fields such as status, labels, milestones, and user-defined fields.
GitHub repositories can now be automatically selected for backup based on custom properties defined by the user in GitHub.
Microsoft 365 groups are now visible in the user list and during backup plan configuration, making backup management and user selection more efficient.
It is now possible to exclude attachments from Jira disaster recovery backups.
Xopero ONE now supports Microsoft SQL databases with longer names (up to 256 characters) during backup.
The log detail level can now be configured using the environment variable XOPERO_LOG_LEVEL. This method is faster and more flexible than the previous approach, which required editing configuration files or creating new images in SaaS environments.
Ability to configure retry attempts for requests to the licensing server has been added.
Docker images and the virtual appliance for VMware have been updated from Ubuntu 20.04 to Debian 11 bullseye, improving the security and stability of the services.
Xopero ONE startup is now faster.
Increased the size and retention of log files for the Management Service and backup agents. Each file can now be up to 30 MB, and the system keeps up to 14 date-stamped files.
Security and efficiency in managing permissions and integration with external identity providers have been improved significantly.
Remote agent updates now have better error logging.
Xopero ONE Management Service will now force password change upon first login.
The system now always requires full two-factor authentication (2FA), which means it can no longer be bypassed using a token stored in the browser. This safeguard provides additional protection against unauthorized access and ensures full session security.
Selection of the target project during restore to Azure DevOps has been improved.
Recovery of incremental Git repository backups and pull requests for GitHub Enterprise Cloud organizations has been optimized.
Error messages during the restoration of environments in GitLab are now clearer and easier to understand.
Increased the maximum supported database name length from 50 to 256 characters.
Xopero ONE now displays a warning when the number of available recovery codes is low. The warning appears when there is one or no recovery code remaining.
Fixed the issue where agent kept disconnecting during recovery of large GitHub repositories.
The notifications on Git organization dashboards now appear correctly and don't overlap.
Fixed an issue where restored GitHub Enterprise Cloud repositories would appear in incorrect order.
Resolved an issue that prevented changing the default worker when adding a new Jira organization to Xopero ONE.
Fixed an issue where an incorrect error message was displayed when registering a GitHub Enterprise Cloud account failed due to access-related problems.
Fixed an issue with restoring relationships between work items and objects in Jira disaster recovery.
Azure DevOps wiki can now be backed up correctly, despite the project type.
Information about throttling and used credentials is now correctly displayed in task logs.
Xopero ONE now supports registering S3 storage in custom regions that were previously unsupported. This enables seamless use of such storage for backups and restorations, improving system flexibility and usability.
Improved how license restrictions are handled for storage in XMS. Previously, these restrictions prevented creating replication plans from Xopero Cloud Storage to external providers like Wasabi. With this update, replication plans can now be created while respecting the applicable license limits.
Resolved an issue where the default worker information was not displayed for certain Xopero Cloud Storage repositories. Previously, this caused an orange warning indicating that no default worker was assigned.
Improved backup task resumption so that after an error, the task continues from the same backup type instead of automatically switching to incremental mode.
Improved the display of backup completion times on the dashboard. The COMPLETED column now shows the actual task completion time rather than the start time, providing a more accurate view of backup progress.
Added a clear message to inform non–primary administrator users that they cannot change login access from the MSP service.
Improved the display of device details for storage replication tasks, resolving the issue where worker information was missing in the management panel.
Improved Hyper-V and file backup tasks so that when access to an SMB server fails, tasks no longer hang and instead complete successfully or are canceled.
Introduced a mechanism that immediately displays information about missing Microsoft 365 licenses when adding additional organizations in Xopero ONE.
Added handling for "Connection reset by peer" errors during VMware backups, preventing tasks from getting stuck. Error details are now properly displayed on the dashboard and recorded in the logs.
The Microsoft SQL backup script has been updated to skip databases in offline mode. This ensures backup tasks run smoothly, securing only available databases without interrupting the entire process.
Fixed an issue where attachments in Microsoft 365 messages were not shown in the preview. Attachments are now correctly displayed when viewing messages in the Xopero ONE interface.
Added support for installing dependencies on openSUSE, with automatic detection of the Zypper package manager.
Fixed a bug that blocked licenses assigned to users of a deleted Microsoft 365 organization when an error occurred during application removal. Licenses are now correctly released, ensuring available licenses are not held unnecessarily.
Fixed an issue that caused backup agents to fail during installation or updates. With the new installer mechanism, all repairs and updates now complete smoothly.
In version 2.1.0, handling of symbolic links in Linux backups was improved. Files and directories referenced by symlinks are now included only when the corresponding option is enabled, preventing unnecessary duplication of data.