After a ransomware attack, Acronis Cyber Protect can restore a typical small business workstation in 1–4 hours from a local backup, or 2–6 hours from cloud storage, for a 100–200GB system. File and folder restores finish in minutes. The biggest variable is not the software — it is where your backup lives and how fast your network is. Restoring from a local NAS over a 1 Gbps connection runs 5–10 times faster than pulling data down over a standard 100 Mbps business internet line. If you are relying solely on cloud backup, plan for the longer end of that window.

Get Acronis Cyber Protect for your business →


What Actually Determines Your Restore Time

Four variables drive most of the difference between a 90-minute recovery and a 6-hour one.

Backup location is the biggest lever. A local NAS or external drive connected to your network delivers 60–100 MB/s in practice. A 100 Mbps internet connection delivers roughly 12.5 MB/s. On a 200GB backup, that gap is the difference between a 35-minute data transfer and a 4.5-hour one.

Data volume is straightforward. A 50GB workstation restores faster than a 300GB server. Typical business workstations run 100–200GB; small servers often hold 300–500GB.

Same hardware vs. new hardware matters at the end of a restore. Acronis's Universal Restore function rewrites drivers when you recover to a different machine — useful when original hardware is destroyed, but it adds 30–60 minutes for driver detection and installation.

File-level vs. full-system restore is the clearest dividing line. Recovering a specific documents folder takes minutes regardless of where the backup lives. Recovering a full disk image takes hours.


Three Real Scenarios with Time Estimates

Scenario 1: One workstation, documents folder only (5–10 GB, local NAS)

A single employee's files are encrypted. The rest of the network is clean. You use the Acronis interface to restore only the affected folder from a local NAS backup.

Estimated time: 5–15 minutes.

The data transfer from a local NAS over 1 Gbps is nearly instant for this volume. Most of the time is spent navigating the interface and confirming the restored files look correct.

Scenario 2: Full system restore, same hardware (150 GB, local NAS)

A critical accounting workstation or small server has a corrupted OS or a full ransomware infection. The hardware still works. You boot from an Acronis USB drive and restore a 150GB image from your local NAS.

Estimated time: 1.5–2.5 hours.

The raw data transfer at 60–100 MB/s takes 25–40 minutes. The rest of that window covers booting from media, running the restore wizard, and the system restarting into a confirmed working state. Owner reports on small business IT forums consistently put this scenario at 2–3 hours under these conditions — the transfer completes quickly, but the boot-and-verify steps add time that spec sheets do not capture.

Scenario 3: Full server restore to new hardware, cloud backup only (200 GB, 100 Mbps internet)

The original server is dead. A replacement arrived. Your most recent backup is in Acronis Cloud. You connect the new machine, initiate Universal Restore, and begin the download.

Estimated time: 5–7 hours.

The math on the download alone: 200,000 MB ÷ 12.5 MB/s = 16,000 seconds, or about 4.4 hours. Add the Acronis boot environment, the restore wizard, Universal Restore's driver detection pass, and the final reboot, and you are looking at 5–7 hours before the server is confirmed operational. This scenario is the clearest argument for keeping a local backup copy alongside cloud storage, even if cloud is your primary offsite protection.


Compare Acronis backup plans and current pricing →


Who Acronis Cyber Protect Is Right For

Use it if:

Look elsewhere if:


How to Keep Your Restore Time as Short as Possible

Run a hybrid backup. Keep a local copy on a NAS or direct-attached drive for speed, and send a second copy to Acronis Cloud for offsite protection. This is the standard 3-2-1 approach: 3 copies, 2 different media types, 1 stored offsite. The local copy handles day-to-day recovery; the cloud copy covers a fire or theft scenario.

Test before you need it. Restore a few files every quarter. Restore a full system to an isolated virtual machine at least once a year. Backups that have never been tested have an unknown failure rate. A test also makes the real event less stressful — you have done it before.

Keep a bootable USB current. A bare-metal restore requires booting outside the failed OS. If you do not have a current Acronis bootable drive ready, you will spend time creating one during the crisis.

Write down the steps. Store a printed or cloud-based recovery checklist somewhere other than the systems that might fail. Anyone in your business should be able to follow it.


Bottom Line

For a typical 100–200GB workstation restored from a local backup, expect 1.5–2.5 hours of downtime. For a server restored from cloud only, plan for 5–7 hours. The restore process itself is straightforward — the time difference comes down to where your backup lives, not how skilled your IT person is.

If keeping a local backup copy is not part of your current setup, that is the most impactful change you can make to your recovery time before a problem happens.

Check current Acronis Cyber Protect pricing →


Related: