Protect your data.
Get back to work.

PCs & Macs

Protect the business information that lives on employee computers, including people who work away from the office.

• File and folder protection for agreed business data.
• Disk or system-image backup where the operating system and backup method support it.
• Scheduling and retention designed around device availability, connectivity, and data volume.
• Recovery: Recover selected files or plan a supported system restore after a device failure or replacement.
• Scope: Device count, operating system, local data, encryption settings, and whether full-system or file recovery is needed.

Physical servers

Connect server protection to the applications and people that rely on it.

• Supported Windows and Linux server workloads.
• Disk, volume, and file backup according to the agreed protection policy.
• Application consistency, credentials, and dependencies reviewed before rollout.
• Recovery: Plan file, volume, or bare-metal recovery on compatible infrastructure, with application validation before handover.
• Scope: Server versions, storage layout, database dependencies, replacement hardware, and recovery priorities.

Virtual machines

Build a recovery plan for the virtual workloads behind your business, with the right protection method for each platform.

• VMware ESXi, Microsoft Hyper-V, and Proxmox VE environments.
• Nutanix AHV, Scale Computing HyperCore, KVM, Red Hat / oVirt, Oracle Linux Virtualization Manager, Citrix / XenServer, and Virtuozzo / Cyber Frame environments assessed by version and backup method.
• Agentless or in-guest protection, with application-aware processing where supported and configured.
• Recovery: Scope whole-VM and granular recovery, destination capacity, networking, and the order in which dependent systems return.
• Scope: Hosts and guest counts, platform versions, storage, cluster design, credentials, licensing, and restore compatibility. Features differ across hypervisors.

Files & network storage

Identify shared business data and choose a supported way to protect it.

• Business file shares and their permissions, owners, and retention needs.
• NAS model, file protocol, agent access, and source compatibility assessed before a recommendation.
• Local and offsite destinations chosen separately from the systems being protected.
• Recovery: Scope file and folder recovery with permission checks and business-owner acceptance. Source backup and using a NAS as a destination are different designs.
• Scope: Model, protocol, file count, used capacity, daily change, permissions, and destination compatibility. Appliance-specific backup is confirmed during discovery.

Cloud servers

Make cloud-hosted infrastructure part of the recovery plan instead of assuming the hosting platform handles every failure.

• Supported Microsoft Azure virtual machines.
• Private-cloud and hosted Windows or Linux workloads using an appropriate supported backup method.
• Storage location, transfer paths, permissions, and recovery destination reviewed together.
• Recovery: Recover the protected workload to an approved, supported destination with identity, networking, and access dependencies addressed.
• Scope: Subscriptions, regions, workload access, provider responsibilities, data transfer, and recovery compute requirements.

Microsoft 365 & Google

Give important cloud collaboration data its own backup and recovery policy.

• Microsoft 365 mailbox, OneDrive, SharePoint, and supported Teams data.
• Google Workspace Gmail, Drive, and supported shared-drive data.
• Tenant authorization, protected users, shared resources, retention, and API limitations reviewed explicitly.
• Recovery: Recover supported items to the permitted account or location. We confirm exactly which objects, permissions, and restore destinations the selected service supports.
• Scope: Existing or new tenant, user and shared-resource counts, required data types, retention, and any tenant migration. Sync, retention features, and backup serve different purposes.

Identity & directory

Plan for the identity services that people and applications need before they can return to work.

• Microsoft Entra ID backup options for supported directory objects and configuration.
• Windows Active Directory protection and recovery planning.
• Administrative access, dependent services, and a documented recovery order.
• Recovery: Review granular directory recovery or an appropriate server and directory restore procedure, with identity validation before dependent apps resume.
• Scope: Tenant and domain structure, supported object types, roles, licensing, restore limitations, and an independently accessible recovery account.

Business applications

Back up business systems in a way that accounts for the application as well as its files.

• Supported Microsoft SQL Server, Microsoft Exchange Server, and Oracle Database workloads.
• Application-aware backup methods, consistency requirements, and log handling where supported.
• Other business applications assessed with their software vendor, including file locations, dependencies, and restore procedures.
• Recovery: Recover the database or application using the supported method, then have the business owner validate that the workflow actually works.
• Scope: Application versions, database size, supported backup agents, transaction requirements, vendor support, and recovery credentials.

Mobile business data

Review selected mobile data that needs protection, alongside the policies that govern the device.

• Supported iOS and Android backup options for selected data categories.
• Permissions, operating-system restrictions, and mobile-app requirements.
• Business data separation and alignment with your mobile-device management policies.
• Recovery: Recover supported data through the chosen mobile backup service. This is separate from a full phone image, device management, and SaaS backup.
• Scope: Device ownership, supported data categories, account access, licensing, and privacy requirements.

Encryption at rest

We configure supported backup encryption and document the algorithm, storage destination, and key or password ownership for each protection policy.

Encryption in transit

We review supported encrypted transfer paths between protected systems, backup services, and storage. Transport settings are checked for the chosen architecture.

Protected recovery copies

We design separate recovery copies and assess immutable retention or isolated storage where supported. Retention locks, administrator access, and deletion behavior are validated.

Controlled access & key custody

We define least-privilege access, MFA where available, recovery credentials, key storage, and authorized restore requests. A recoverable key must be available when it is needed.

HIPAA support

Coordinate BAAs, access, retention, and recovery evidence with your compliance owner.

Quantum-resistant encryption

Acronis describes AES-256 with strong credentials as quantum-resistant backup encryption where supported. This does not mean every connection uses post-quantum public-key cryptography.

Ransomware recovery planning

We connect backup with incident containment, selection of a suitable recovery point, and supported malware checks. Recovery proceeds into a prepared environment with security review.

Restore testing & evidence

We test the agreed recovery method, record what was restored and validated, and track exceptions. A successful backup job is one signal; usable business recovery is the outcome.

Recovery objectives

Agree the target data-loss window (RPO) and recovery time (RTO), then test the design. These are planning objectives, not automatic guarantees.

Disaster recovery

Standby compute, failover, networking, and failback are scoped separately from backup storage.