Windows, Linux and macOS
Windows, Linux and macOS: agents and features depend on the version and support matrix.
Structure Acronis backup, restoration, storage, policies and operational response without confusing a single console with automatic coverage of every risk.
Cyber Protect and Cyber Protect Cloud assessed according to contracted workloads, storage, security, DR and licenses.

Acronis Cyber Protect combines backup and endpoint protection capabilities in specific offerings and editions. Acronis Cyber Protect Cloud targets service providers and multitenant operations, with services and Advanced Packs enabled according to the contract. Similar names do not make features, consoles, storage and licenses interchangeable. The project confirms product, edition, deployment, version, workloads and add-ons before defining the architecture. Antimalware, EDR, DLP, email security, management or disaster recovery features must not be assumed to be included in every subscription.
Protection plans can combine backup and other enabled modules for supported devices or workloads. Grouping functions reduces administration points but increases the need for change control: a change can affect protection, windows, retention or endpoint behavior. Add Solution separates policies by criticality, workload type, connectivity and owner. Frequency, backup scheme, retention, destination, encryption, exclusions and schedule are documented. Inheritance and bulk assignment are reviewed to prevent broad changes from degrading systems with different requirements.
In a compatible deployment, agents perform operations on workloads and communicate with the management server or cloud service. Exact components and functions vary between Cyber Protect and Cyber Protect Cloud. Proxies, appliances or specific integrations may be used in virtual environments according to the supported platform. The design addresses DNS, ports, certificates, accounts, updates, credentials, bandwidth and storage access. Losing the console must not mean losing the knowledge required for recovery: configuration, inventory, keys and procedures receive their own protection and documentation.
A commercial platform list does not replace documentation of versions and limitations.
Windows, Linux and macOS: agents and features depend on the version and support matrix.
VMware vSphere and Microsoft Hyper-V: VM protection can use specific integrations, accounting for permissions, snapshots, agents and consistency.
Applications: supported databases and applications may require credentials, VSS or dedicated procedures for consistency and granular restoration.
Microsoft 365 and Google Workspace: cloud-to-cloud protection, covered services, authentication, APIs and retention vary by offering.
Cloud and physical servers: destination, egress, networking and recovery method must be validated in the actual environment.
Backups can use Acronis Cloud Storage and supported local or third-party destinations, depending on the product and configuration. Capacity is calculated from protected volume, change rate, frequency, retention, full backups, compression, growth and additional copies. An off-site copy reduces site dependency but introduces bandwidth, latency, egress, residency and recovery-at-scale considerations. Local storage can accelerate restores but requires physical, logical and capacity protection. The architecture combines destinations only when they address different loss events. Immutability or deletion protection depends on the documented service, region, edition and configuration. No Acronis destination is assumed to be automatically immutable. Periods, credentials, keys and administrative accounts remain relevant.
Acronis offerings may include antimalware, ransomware protection, vulnerability assessment, patch management, EDR or other modules. Availability and depth vary by edition, Advanced Pack, operating system and license. These features can complement endpoint and backup operations but do not automatically replace the customer’s identity architecture, firewall, SIEM, incident response or other controls. This page keeps Acronis within the Backup & DR context; cybersecurity requirements receive their own assessment and defined integration. Exclusions, quarantine and automatic actions are tested against critical applications. The same account must not unnecessarily concentrate tenant administration, endpoint administration and backup deletion authority.
Workflows can include restoration of files, volumes, machines and applications, and recovery options for different hardware or platforms where supported. Universal Restore can help inject drivers and adjust startup in compatible scenarios; it does not guarantee that applications, licenses, networking and integrations will operate at the destination. Testing measures recovery-point location, read time, transfer, boot, consistency and owner validation. For bulk restoration, bandwidth, APIs, compute and destination capacity are tested. Evidence records the point used, duration, exceptions and corrective actions.
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
Testar consistência, restore, capacidade do destino e aceite do owner.
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
Acronis Disaster Recovery can provide recovery on cloud infrastructure for supported workloads and configurations, usually as a contracted capability or pack. Scope, region, compute, networking, IPs, VPN, runbooks, testing and billing must be confirmed. RPO and RTO depend on frequency, replication, connectivity, reserved or available capacity, startup and dependencies. The plan includes failover, validation, communication and failback. External services such as identity, DNS, databases, SaaS and telecommunications require explicit treatment.
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
Testar consistência, restore, capacidade do destino e aceite do owner.
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
Protection of supported SaaS data depends on authentication, API permissions, licensed services and provider limits. Mailboxes, drives, sites, teams or other objects must not be assumed without validating the current offering’s scope. The project defines active and offboarded users, discovery of new users, retention, search, restore authority and residency. Native SaaS retention, archiving and independent backup serve different objectives.
Cyber Protect Cloud organizes operations by partners, customers and tenants according to the provider’s model. The hierarchy facilitates policies and services but requires least-privilege roles, MFA where supported, technician segregation, an audit trail and an offboarding process. Quotas, storage, enabled services and branding are not merely commercial settings: they can affect protection and support. A global template must accommodate controlled exceptions. Each tenant retains identifiable owners, contacts, criticality and runbooks.
Operations monitor missing backups, the age of the latest recovery point, recurring failures, duration, volume changes, retention, storage, offline agents and tests. Alerts must reach the accountable queue with a priority and deadline. Agent, console or integration updates are evaluated against compatibility and the change window. Growth may require adjustments before retention is reduced by a physical or commercial limit. Executive reports show coverage, risk and testing; technical metrics remain available for diagnosis.
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
Testar consistência, restore, capacidade do destino e aceite do owner.
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
Acronis markets offerings, editions and Advanced Packs with different scopes. Metrics may be based on workload, device, user, capacity, service or consumption, according to product and contract. Cloud storage, DR compute, traffic, extended retention and advanced modules may generate separate charges. Features vary by operating system, hypervisor, region, tenant and version. Licenses for applications and systems restored at the destination remain the customer’s responsibility. Add Solution, Acronis and any service provider have their own support scopes and SLAs; this page asserts no partnership level, response level or availability commitment.
Answers for Acronis protection, recovery and operational decisions.
No. Features depend on the product, edition, Advanced Packs, workload and contracted license.
No. They share concepts and technologies, but deployment model, multitenancy, catalog and licensing differ.
This must not be assumed. The feature must be confirmed for the specific service, region, edition and configuration, including the period and deletion authority.
No. Backup provides recovery capability. Any licensed security modules complement controls, but their coverage must be assessed in the security design.
No. It can support system adaptation in supported scenarios; drivers, licenses, networking, dependencies and the application must be validated.
Not without design and testing. Frequency, networking, compute, capacity, dependencies and procedures determine the observed outcome.
Native retention and external backup have different objectives. The requirement must be based on loss events, timeframe, restore authority and customer obligations.
Rarely. Criticality, volume, connectivity, system, retention and ownership justify groups and controlled exceptions.
backup and recovery assessment;
Cyber Protect or Cyber Protect Cloud architecture;
tenant, component and agent design;
protection plans and retention;
local storage, cloud storage and off-site copies;
protection for supported workloads, Microsoft 365 and Google Workspace;
disaster recovery, testing and runbooks;
monitoring, capacity, updates and ongoing operational support.
Connect Acronis policies, destinations, security, DR and operations to actual service requirements.