Information about the Xopero ONE backup solution, including its architecture and framework.

Examine the core architecture and primary components of Xopero ONE software.

Review third-party software dependencies and open-source licenses in Xopero ONE.
Examine the core architecture and primary components of Xopero ONE software.
The Xopero ONE architecture relies on a modular, multi-tier framework comprising the central management service, backup agents, and scalable storage targets.
A backup solution is a software system or service that creates and stores copies of data so it can be restored if the original data is lost, corrupted, deleted, encrypted by ransomware, or otherwise becomes unavailable.
Xopero specializes in enterprise backup, disaster recovery, and cyber-resilience solutions. One of our flagship products, Xopero ONE, provides comprehensive data protection across a wide range of physical, virtual, and cloud environments. This solution enables organizations to protect business-critical data from accidental deletion, hardware failures, ransomware, cyberattacks, and other data-loss events.
Xopero ONE is designed to protect data across physical machines, virtual environments, databases, cloud services (Microsoft 365), SaaS applications (such as Jira and Confluence), and different DevOps platforms. It consists of two primary components: the management panel and the backup agent. The solution also requires a storage repository to store backup data. This storage can be managed by the user or provided by Xopero (i.e., Xopero Cloud Storage, Xopero Unified Protection).
The management system is used for administration and configuration, while the backup agents handle the actual execution of all backup-related operations. When a backup task is initiated, the management service dispatches the job to the backup agent, which performs the requested operation. Once the task is completed, the agent transmits the execution results and logs back to the management system, where administrators can review them in the web console.
The centralized management interface of Xopero ONE is the Xopero ONE Management Service (XMS). It enables administrators to comprehensively manage backups and related resources through the web console. In the on-premises deployment model, XMS can be installed on supported Windows and Linux operating systems, deployed in a Docker environment, or hosted directly on compatible NAS devices. In the SaaS deployment model, the management service runs on Xopero's cloud infrastructure.
Regardless of the deployment model, the platform provides identical features and functionality through a unified user interface. The management panel is divided into separate modules, each of them dedicated to a different aspect of backup management, such as backup plans, storage, and backup tasks.
A backup agent is a lightweight software installed on a protected server, virtual machine, laptop, or cloud instance. It reads source data and transfers it to the designated storage destination.
Xopero ONE backup agents (also referred to as workers in the Xopero ONE environment) perform all operations requested by the Xopero ONE Management Service, including processing data (such as encryption and compression), browsing storage repositories, transferring data directly to the storage, and restoring data.
Agents execute backup and recovery operations directly and do not transfer backup data through the management panel. They are also responsible for integrating with virtualization hosts, and performing all other data-processing and infrastructure-related tasks within the system.
Depending on the deployment model and protected resources, administrators can deploy various backup agents, including the cloud worker, feature worker, local worker, endpoint agent, server agent, and virtual agent.
A data storage system is a medium designed to persistently retain and manage collections of data so that they can be retrieved and used later. Storage technologies span physical media, such as solid-state drives (SSDs) and hard disk drives (HDDs); deployment models, including cloud and hybrid cloud; and systems purpose-built for workloads such as artificial intelligence (AI) and edge computing.
In Xopero ONE, a storage repository is a designated destination used to persistently retain, organize, and protect backup data for subsequent retrieval and disaster recovery. The solution features a multi-storage architecture that supports storing backup data on-premises (local disks, SMB, NFS, and iSCSI targets), in cloud repositories (Xopero Cloud Storage, AWS, and S3-compatible storage), or in a hybrid model.


Review third-party software dependencies and open-source licenses in Xopero ONE.
Xopero ONE incorporates third-party software libraries to power core system functions, including data encryption, network communication, storage interface operations, and data compression.
The table below outlines all third-party libraries used by Xopero ONE.
@fortawesome/fontawesome-svg-core
Font Awesome Free License
@fortawesome/free-brands-svg-icons
Font Awesome Free License
@fortawesome/pro-duotone-svg-icons
Font Awesome Pro License
@fortawesome/pro-light-svg-icons
Font Awesome Pro License
@fortawesome/pro-regular-svg-icons
Font Awesome Pro License
@fortawesome/pro-solid-svg-icons
Font Awesome Pro License
@microsoft/signalr
Apache 2.0
@ng-select/ng-select
MIT
@ngrx/effects
MIT
@ngrx/store
MIT
AgileObjects.ReadableExpressions
MIT
AlphaVSS
Apache 2.0
angular-i18next
MIT
AutoMapper
MIT
AWSSDK.S3
Apache 2.0
chart.js
MIT
chartjs-plugin-datalabels
MIT
coverlet.collector
MIT
DiscUtils
MIT
FirebirdSql.Data.FirebirdClient
Developer's Public License Version 1.0
FluentFTP
MIT
FluentScheduler
BSD (3-clause)
FubarDev.FtpServer
MIT
Hali4831.MixERP.Net.VCards
Apache 2.0
i18next
MIT
i18next-browser-languagedetector
MIT
i18next-http-backend
MIT
Ical.Net
MIT
iSCSIConsole
LGPL 3.0
JsonLogic.Net
MIT
jwt-decode
MIT
K4os.Hash.xxHash
MIT
LightningDB
OpenLDAP Public License
LiteDB
MIT
LZ4
BSD (2-clause)
MailKit
MIT
Microsoft.AspNet.WebApi.Client
Microsoft EULA
Microsoft.AspNetCore
Apache 2.0
Microsoft.AspNetCore.Authentication.JwtBearer
Apache 2.0
Microsoft.AspNetCore.CookiePolicy
Apache 2.0
Microsoft.AspNetCore.Hosting
Apache 2.0
Microsoft.AspNetCore.Http.Connections
Apache 2.0
Microsoft.AspNetCore.Identity
Apache 2.0
Microsoft.AspNetCore.Identity.EntityFrameworkCore
Apache 2.0
Microsoft.AspNetCore.Identity.EntityFrameworkCore
Apache 2.0
Microsoft.AspNetCore.Identity.EntityFrameworkCore
Apache 2.0
Microsoft.AspNetCore.Mvc.Core
Apache 2.0
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Apache 2.0
Microsoft.AspNetCore.Mvc.Testing
Apache 2.0
Microsoft.AspNetCore.Razor.Design
Apache 2.0
Microsoft.AspNetCore.Server.Kestrel
Apache 2.0
Microsoft.AspNetCore.SignalR
Apache 2.0
Microsoft.AspNetCore.SignalR.Client
Apache 2.0
Microsoft.AspNetCore.SignalR.Protocols.NewtonsoftJson
Apache 2.0
Microsoft.AspNetCore.SpaServices
Apache 2.0
Microsoft.AspNetCore.SpaServices.Extensions
Apache 2.0
Microsoft.AspNetCore.StaticFiles
Apache 2.0
Microsoft.CodeAnalysis.Common
MIT
Microsoft.CSharp
MIT
Microsoft.EntityFrameworkCore.Design
Apache 2.0
Microsoft.EntityFrameworkCore.InMemory
Apache 2.0
Microsoft.EntityFrameworkCore.InMemory
Apache 2.0
Microsoft.EntityFrameworkCore.Proxies
Apache 2.0
Microsoft.EntityFrameworkCore.Sqlite
Apache 2.0
Microsoft.EntityFrameworkCore.Sqlite
Apache 2.0
Microsoft.Extensions.Hosting.WindowsServices
Apache 2.0
Microsoft.Extensions.Identity.Stores
Apache 2.0
Microsoft.Extensions.Localization.Abstractions
Apache 2.0
Microsoft.Extensions.Logging.Configuration
Apache 2.0
Microsoft.Extensions.Logging.Console
Apache 2.0
Microsoft.Extensions.Logging.Debug
Apache 2.0
Microsoft.Graph
MIT
Microsoft.Identity.Client
MIT
Microsoft.Identity.Client
MIT
Microsoft.NET.Test.Sdk
Microsoft EULA
Microsoft.NET.Test.Sdk
Microsoft EULA
Microsoft.NETCore.App
MIT
Microsoft.NETCore.App
MIT
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Microsoft EULA
Microsoft.VisualStudio.Web.CodeGeneration.Design
Apache 2.0
Microsoft.Win32.Registry
MIT
Mono.Posix-4.5
MIT/BSD-3/Microsoft Patents
Mono.Posix.NETStandard
MIT/BSD-3/Microsoft Patents
Moq
BSD (3-clause)
Moq
BSD (3-clause)
MSTest.TestAdapter
MIT
MSTest.TestAdapter
MIT
MSTest.TestFramework
MIT
MSTest.TestFramework
EULA Microsoftu
NETStandard.Library
MIT
NETStandard.Library
MIT
Newtonsoft.Json
MIT
Newtonsoft.Json
MIT
ng-click-outside
MIT
ng2-charts
ISC License
ngx-toastr
MIT
NLog.Web.AspNetCore
BSD (3-clause)
Npgsql.EntityFrameworkCore.PostgreSQL
PostgreSQL License
OpenSSL.Net
BSD
protobuf-net
Apache 2.0
RestSharp
Apache 2.0
Rnwood.SmtpServer
BSD (3-clause)
rxjs
Apache 2.0
SharpCifs.Std
LGPL 2.1
SMBLibrary.Std
LGPL 3.0
Swashbuckle.AspNetCore
MIT
System.IO.FileSystem.AccessControl
MIT
System.Management
MIT
System.Reactive
MIT
System.Text.Json
MIT
tslib
BSD (0-clause)
tsutils
MIT
UnQLite
BSD (2-clause)
uuid
MIT
Vibrant.InfluxDB.Client
MIT
VMware SDK
Proprietary
xunit
Apache 2.0
xunit.runner.visualstudio
MIT
zone.js
MIT
Zstandard
BSD (3-clause)