All pages
Powered by GitBook
1 of 1

Loading...

Xopero ONE 2.4.0

Release 2.4.0, featuring Linux image-level backup, FIPS-compliant encryption, and Active Directory integration.

PREVIOUS RELEASESRELEASE 2.4.0 (VIDEO)

🆕 NEW FEATURES

Disk backup support for Linux

Added support for disk-level backups on Linux systems. This feature allows for full and incremental protection of physical Linux machines without snapshot-level integration (e.g., LVM/BTRFS), ensuring cross-platform consistency for heterogeneous environments.

Linux Image Backup in Xopero ONE | Full Linux System Protection

Active Directory integration via LDAP

Added Active Directory LDAP integration featuring automated user provisioning upon login, group-to-role mapping, and administrative fallback authentication for high availability.

Xopero ONE & Active Directory Integration (LDAP) | User Management Automation

FIPS-compliant encryption support

Introduced a new FIPS mode for backup plans using AES-CBC encryption. When enabled, the system ensures that encryption is performed exclusively via FIPS-validated modules on supported Windows backup agents, providing enhanced security compliance for regulated environments.

FIPS Compliant Encryption in Xopero ONE | Government-Grade Security

German language support

The Xopero ONE Management Service is now available in German. This localization covers all dashboard views, organization settings, and backup plan configurations, delivering a fully native user experience for the DACH region.

Added support for backup and recovery of Azure DevOps Test Plans (including test suites). This includes preservation of test case relationships, configurations, and execution history, ensuring complete protection of the quality assurance lifecycle within DevOps projects.


The pre- and post-backup script mechanism now supports a new XOPERO_BACKUP_TYPE argument. This allows custom scripts to dynamically identify the current backup type (full, incremental, differential, or synthetic full) and execute conditional logic based on the operational scope.

Implemented detailed installer logging for Windows-based backup agent remote updates. Logs are now stored locally on the endpoint alongside standard agent logs, providing enhanced visibility into update failures and significantly simplifying troubleshooting.

Changed SharePoint site and template search functionality to be case-insensitive. Users can now find and select resources for backup using any combination of uppercase and lowercase letters, simplifying the search process.

Redesigned the repository exclusion mechanism in backup plans to improve clarity and control. Users can now efficiently manage which repositories are excluded from protection and receive immediate visual feedback on active exclusion rules.

Updated localization strings across the Xopero ONE Management Service panel to align with the latest official Atlassian terminology. This ensures a consistent user experience for customers operating Xopero ONE alongside Jira and Confluence, particularly regarding space and work item naming conventions.

Enhanced Azure DevOps integration stability by properly handling negative timeout values. Invalid timeout parameters received from the service provider are now ignored rather than causing task failures, ensuring uninterrupted backup processes.

Xopero ONE now automatically retries Jira API requests when encountering network-related errors (such as socket exceptions or connection resets). By default, the system performs up to five retry attempts using an exponential backoff strategy (1s, 2s, 4s, 8s, and 16s), which significantly improves the stability of backup and restore operations for large Jira instances or unstable network environments.

Enhanced the granularity and accuracy of error logs during the restoration of Jira work item types. If specific work item configurations cannot be fully restored due to target environment mismatches, the system now provides explicit, contextual details, allowing administrators to rapidly isolate and resolve data mapping issues.

Azure DevOps synchronization is now significantly faster, especially for environments with access to multiple organizations. This update eliminates past performance degradation, slashing synchronization times from up to 10 minutes down to approximately 10 seconds for standard Azure DevOps environments.


Replication scripts now correctly handle passwords containing special characters (such as quotes, dollar signs, and brackets). This fix ensures that pre- and post-task scripts, particularly those used for iDRAC integration, execute successfully regardless of password complexity.

The system now correctly differentiates between standard Microsoft 365 users and shared mailboxes, ensuring that shared mailboxes are accurately identified and licensed during organization synchronization, eliminating the need to remove and re-add the organization to update mailbox statuses.

Fixed an issue where PostgreSQL backup tasks could falsely report a successful status even when no data was secured. Backup tasks now correctly terminate with an error or warning status upon failure, including scenarios involving invalid credentials or execution timeouts.

Resolved an issue where storage destinations without a defined capacity limit (unlimited) rendered incorrectly in the Xopero ONE Management Service dashboard. Previously, these were falsely displayed as 100% full with a low space badge; they now correctly display an infinity symbol (∞) and no longer trigger misleading low-space warnings.

The predefined backup plan modal dialog no longer incorrectly displays onboarding steps when adding subsequent organizations. The onboarding progress bar is now strictly reserved for the initial setup, ensuring a cleaner, distraction-free interface for experienced users.

The last backup task summary chart now features an auto-scaling, dynamic Y-axis. Previously constrained to a fixed range of 0–280, the chart now automatically scales based on the highest data point, ensuring that large-scale datasets are never visually clipped and low values remain highly readable.

Fixed a bug where assigning a backup agent to a backup plan triggered the automatic creation of folders across all local storage destinations. Directories are now created strictly on-demand when a storage destination is actively utilized by a task, preventing the accumulation of empty folders across the file system.

Fixed an issue where Git LFS (Large File Storage) objects with .txt and .html extensions were not being correctly secured. The system now properly identifies and backs up these specific file types within the LFS framework, ensuring complete repository data integrity.

Resolved an issue with GitHub App integration, where repositories were automatically disconnected upon encountering transient authorization errors. The system now safely maintains the repository connection and automatically retries the synchronization, eliminating the need for manual administrative intervention.

Fixed an issue where custom field values within Jira work items were not correctly restored. All metadata associated with custom fields is now accurately preserved during the restoration process.

Resolved an issue where archived Confluence spaces were restored as active spaces and missing critical components such as folders, smart links, boards, and databases. Archived status and all associated content types are now correctly preserved during recovery.

Fixed an issue where Jira active spaces which were previously marked as deleted or archived were not restored to an active state, even if they had been reactivated in Jira before the last backup. The system now correctly synchronizes and restores active status for all spaces.

GitHub repository restoration now correctly handles environments with a high volume of branches (exceeding 500). This update resolves a "Bad request" error that previously occurred during incremental restoration for complex repository structures, ensuring reliable recovery regardless of branch count or backup type.

Jira restoration now correctly preserves custom screens associated with workflow transitions. When a space is recovered or migrated to a new instance, transitions configured to show a screen accurately maintain their original screen associations, provided the target screens are part of the space's screen scheme.

Jira restoration now correctly preserves field mapping rules within workflow transitions, including configurations that copy custom field values from parent work items. This fix ensures that restored workflows maintain their original operational logic, enabling seamless creation and recovery of sub-tasks that depend on these transition behaviors.

Jira backup plans now correctly process JQL exclusion rules based on creation date, modification date, and specific field values. This update ensures work items are accurately filtered according to the defined criteria and resolves an issue where work items with empty field values were unintentionally excluded when using certain JQL operators.

Confluence restoration now correctly preserves statuses assigned to draft pages and blog posts. All draft content in the restored space retains its original workflow status, ensuring consistency between the source and restored environments.

Azure Test Plans backup and recovery

🔨 IMPROVEMENTS

Information about backup type in pre-backup scripts

Remote update installer logs for Windows backup agents

Case-insensitive SharePoint site search

Repository exclusion mechanism

Standardized Atlassian terminology localization

Handling negative Azure DevOps timeout values

Enhanced network resilience for Jira backup and recovery operations

Jira work item types restoration logs

Performance improvement for Azure DevOps synchronization

🐛 BUGFIXES

Special character support for passwords in replication scripts

Microsoft 365 shared mailbox identification and licensing

PostgreSQL backup failure reporting

Storage capacity display on the management system dashboard

Onboarding steps in the predefined backup plan modal

Last backup task summary chart scaling

Local storage folder creation triggered by backup agent assignment

Git LFS text and HTML file backup

GitHub repository synchronization (GitHub App integration)

Jira custom field value restoration

Archived Confluence spaces restoration

Restored Jira space status synchronization

Restoration of GitHub repositories with many branches

Restoration of workflow transition screens in Jira

Restoration of field mapping rules in Jira workflows

JQL-based work item exclusion in Jira backup plans

Restoration of Confluence draft content status

Azure DevOps Test Plans Backup in Xopero ONE | QA & Test Suites Protection