Both free tiers stop short of a finished disaster-recovery platform. AOMEI keeps dissimilar-hardware restore, differential backups, and automated image cleanup behind its paywall. The choice comes down to which job would be hardest to replace on the morning a machine dies.
Quick Take
- Image-first Windows office: AOMEI Backupper Standard. System, disk, partition, and file images; daily, weekly, or monthly schedules; bootable WinPE media; local, NAS, and cloud targets at 0 dollars.
- Cloud-first document office: CBackup. Scheduled cloud jobs across Google Drive, OneDrive, Dropbox, and CBackup’s own space, plus a way to combine the free quota you already hold.
- Hybrid shop: both. AOMEI covers the machine image; CBackup covers the document copy that leaves the building.
- Multi-seat or DR-heavy office: neither free tier, until you have verified licensing, retention, and central deployment on the paid plans.
What Makes a Free Backup Tool Business-Capable
Start with one question: can the tool capture a consistent copy of data while people are still working in it? On Windows, that consistency comes from the Volume Shadow Copy Service, which coordinates three roles: a requester (normally the backup application), a writer (the application that owns the data, such as SQL Server), and a provider that creates the point-in-time copy. When all three support VSS, application data can be backed up without taking the application offline, per Microsoft’s VSS documentation.
What matters at purchase is whether the engine behaves as a VSS requester on your own workload. AOMEI says you can image a running PC without closing applications, which describes the outcome every buyer wants; CBackup’s product pages say nothing about open files. Either way, run the test before you depend on the tool: leave a spreadsheet or a line-of-business database file open and locked, run the job, restore it, and open the result. A clean restore answers the question that a feature badge leaves hanging.
Encryption needs the same hands-on check. Zero-knowledge, or client-side, encryption scrambles the archive on your own machine and keeps the passphrase out of the provider’s hands, so the business holds the only key that opens it. That is the strongest posture on offer and the least forgiving: lose the passphrase and the backup is unrecoverable, whoever you call. Free editions often reserve their strongest ciphers for paid plans, a caution that reviews of free backup tiers repeat often, so read the encryption setting in the client you install and keep a copy of the passphrase somewhere other than the backup itself.
| Criterion | What to check | What it prevents |
|---|---|---|
| Open-file consistency | Does the engine behave as a VSS requester, and which application writers does it handle? | A file set captured mid-write that restores corrupted. |
| Backup scope | System image, whole disk, partition, or selected folders only? | Discovering after a crash that you saved documents but not a bootable machine. |
| Job types and scheduling | Full, incremental, differential; one-time through monthly; retention or cleanup rules. | Unbounded storage growth and recovery points too sparse to matter. |
| Encryption and key custody | Which standard, applied in transit and at rest, and who holds the passphrase. | An unrecoverable backup after a lost key, or a compliance gap. |
| Restore targets | Same disk, replacement disk, dissimilar hardware, single file, virtual machine. | A backup you cannot actually deploy onto the hardware you have. |
| OS coverage | Windows client, Windows Server, macOS, Linux. | A tool that covers the office workstations but not the one Mac in accounting. |
| Licence and fleet management | Commercial-use terms, per-seat rules, central console, scripted deployment. | A per-PC manual chore that collapses at the fifth machine. |
Five traps recur often enough to name before you install anything.
- A 0 dollars edition may restrict use to personal contexts. Some no-cost editions exclude commercial use. Read the EULA before an install spreads across workstations.
- Headline feature lists and edition tables disagree. A feature can appear in a marketing headline while the edition table shows it behind an upgrade badge. Trust the table.
- A completed job proves the copy exists. Only a restore test proves you can get the data back.
- “Unlimited” cloud storage is quota arithmetic with better copywriting. It means aggregating free space from linked accounts, subject to each provider’s terms.
- Imaging pages rarely describe application consistency. If you run a database or line-of-business app, get the VSS answer in writing before you rely on an image.
AOMEI Backupper Standard: Image-First Windows Backup
This is the free tier to open first when the job is to get a PC back to a working state. AOMEI’s free edition covers system, disk, partition, and file backup, runs full and incremental jobs on daily, weekly, or monthly schedules, and writes to internal disks, external drives, USB media, network shares, NAS, and cloud drives including Dropbox, Google Drive, and OneDrive. It creates WinPE bootable media, which is the piece that matters when Windows will not start.
| Item | Free Standard edition |
|---|---|
| Price | 0 USD; Professional from 39 USD.95, Workstation from 49 USD.95 |
| Operating system | Windows 11 / 10 / 8.1 / 8 / 7 |
| Backup scope | System, disk, partition, and file backup |
| Job types | Full and incremental; daily, weekly, or monthly schedules; event-triggered and USB-plug-in jobs |
| Destinations | Internal disk, external disk, USB, network share, NAS, cloud drives, CD/DVD |
| Recovery | WinPE bootable media creation; file, system, disk, and partition restore |
| Task speed | Paid editions read data from the hard drive faster than Standard, and paid differential backup shortens repeat jobs |
| Paid gates | Universal Restore to dissimilar hardware; differential backup; automatic backup-scheme cleanup; system clone and OS migration; adding the recovery environment to the Windows boot menu |
| Cloning limit | Free edition clones a data disk only |
The paid gates matter more than the feature list, because they sit exactly where disaster recovery gets hard. Universal Restore lets an image boot on a replacement machine with a different chipset. Without it, your free image is a same-hardware recovery plan: fine when a drive fails inside an identical chassis, awkward when a laptop is stolen and its replacement is a different model. Differential backup and automatic cleanup are conveniences you can live without, though the cleanup gate means someone deletes old images by hand.
AOMEI’s free-tier materials state no backup-archive encryption standard for the Standard edition, so treat encryption as something to configure and confirm in the client. If your insurer, client contract, or sector rules require ciphers on stored images, switch encryption on during installation and prove it with a restore that demands the passphrase. Where encryption is a hard requirement, price the upgrade or pair AOMEI with a tool that states its standard plainly. The AOMEI Backupper Standard download page lists the current feature matrix if you want to check a specific capability before installing.
For an office with one to five Windows PCs, a USB or NAS target, and an IT coordinator who can test a boot disc once a quarter, this is a credible starting point. For a fleet that needs to push images to ten machines, the paid editions list PXE boot and image deployment tools, which sets your budget line honestly.
CBackup: Cloud-First Backup and Quota Combination
This is the free tier to open first when the data that matters already lives in a cloud account. CBackup installs on Windows, connects to Google Drive, OneDrive, Dropbox, and FTP destinations, and runs one-time, daily, weekly, or monthly jobs. It also lists cloud-to-cloud backup and cloud storage combination among its features.
| Item | Free | Basic | Premium |
|---|---|---|---|
| Cloud space | 10GB | 1TB | 5TB |
| Public-cloud transfer | 50GB | 2TB | Unlimited |
| Price | 0 USD | 4 USD.99/month or 29 USD.94/year | 14 USD.99/month or 89 USD.94/year |
| Operating system | Windows only | ||
| Schedules | One-time, daily, weekly, monthly | ||
| Task speed | No speed tiers or throttling stated across plans | ||
| Encryption claim | Vendor states 256-bit AES | ||
| Cloud features | Cloud-to-cloud backup; cloud storage combination; file filters; email notifications | ||
Read the free plan as a trial with a hard ceiling. Its included space holds a healthy document share and very little else, and the transfer allowance caps how much data you can move between clouds each period rather than how much you can store. The moment an office wants to protect a photo library or a design archive, the plan pushes toward Basic and the annual subscription becomes the realistic entry cost. CBackup protects files and cloud copies; it ships no disk-imaging engine, so it will not revive a dead workstation on its own.
Confirm the encryption setting in the client you actually deploy. Run one job with encryption switched on, restore it with the passphrase, and keep a copy of that passphrase offline; an encrypted backup nobody can open is worse than a plain one you can read. CBackup’s own business computer backup article sets the free and paid tiers side by side if you want the current plan table.
Set up a pooled cloud destination and prove it works
CBackup’s combination feature merges the free space of several linked cloud accounts into one backup destination. The pool is only as large as what those accounts still have free, and it inherits every provider’s terms, so the setup is worth an hour of arithmetic before the first real job.
Prerequisites
- A CBackup account with the Windows desktop app installed
- Two or more supported cloud accounts with known remaining free space
- Each provider’s terms, checked for restrictions on backup or non-personal use
- A small test folder you can restore without consequence
- Inventory the space each account actually has. Open each provider’s storage settings and write down the remaining free gigabytes, subtracting anything the account already holds. The pool’s ceiling is that sum, whatever plan size the marketing pages print.
- Connect the accounts through the OAuth flow. Authorise each provider from inside the CBackup app; the vendor says it uses the standard OAuth system for account security. Stop and fix any authorisation that does not complete, because a half-linked pool produces confusing destination errors later.
- Build the combined destination and record the arithmetic. Note which accounts are in the pool and how much each contributes. That record defines the blast radius if one provider suspends an account or changes its free tier.
- Run a small job into the pool. Use a test folder large enough to span more than one underlying account where possible, so you learn how data is distributed across providers instead of assuming a single bucket.
- Restore a file and open it. Compare the restored copy against the source and confirm you can identify which provider held it. A restore that opens correctly is the only evidence that the pool works as backup storage.
Verify the result
- The restored test file opens and matches the original
- Every linked account appears in the destination configuration
- The job finished without an out-of-space error
- You can state in writing how much of the pool each provider contributes
- You know what happens to the backup if one linked account is disconnected
The OAuth consent screen fails or loops
Usually a blocked consent screen or the wrong account already signed in. Retry in a clean browser profile and confirm you are authorising the Google or Microsoft account that actually holds the free space.
The backup lands somewhere unexpected
The task may be pointed at a different destination than you intended. Check the task’s destination field before the first run; changing it after a job has started can leave a second copy behind.
Space runs out despite several linked accounts
The sum of free space is smaller than assumed, or one provider’s quota is partly reserved for its own sync client. Recheck each account’s remaining space and drop the ones contributing almost nothing.
You cannot tell whether older versions survive
Assume the pool tracks the source until you prove otherwise. Keep a separate versioned archive, then delete a throwaway file, run the job, and try to recover the earlier version before you rely on retention.
Warning
CBackup’s unlimited-storage pitch describes combining free space from multiple linked drives; CBackup calls unlimited “the most ideal state.” Capacity depends on how much free space each account still holds and on each provider continuing to offer it. Budget the pool at its arithmetic sum, then discount it.
The unlimited online backup feature page explains how accounts are linked and why more drives mean more space. Useful context, and a reminder that the pool is a convenience built on other companies’ free tiers, which can change without notice.
Cloud-to-Cloud DR: What It Solves and What It Does Not
A cloud-to-cloud job copies files that already live in one account into another destination. For an office with years of documents in a single Google Workspace or Microsoft 365 tenant, that second copy reduces dependence on one vendor’s availability, one account’s billing status, and one administrator’s credentials. If the account holding your only copy gets suspended, a scheduled copy elsewhere is the difference between an inconvenience and an incident.
A copy job does not, on its own, undo a deletion. Assume the second copy follows its source until you prove it does not: delete a throwaway file, run the job, and try to recover the earlier version. If the copy mirrors the deletion, you need a version-retention rule stated in writing by the vendor, plus a separate archive that covers the gap. A business that needs roll-back protection needs a rule it has tested, held to a retention policy it can show an auditor.
Info
Cloud-to-cloud coverage and bare-metal recovery answer different failure modes. A document copy cannot boot a dead workstation, and a disk image sitting on a NAS does not survive a fire in the same room. Plan one of each.
A workable cross-cloud DR setup carries these properties:
- The second copy lives in a different provider and a different account from the primary, with separate credentials.
- Someone has deleted a test file and restored it successfully, and the time taken is written down.
- A bare-metal image exists separately for every machine you would need to rebuild.
- Account recovery details (recovery email, phone number, break-glass administrator) sit somewhere a departing employee cannot take them.
- The restore procedure is documented well enough that a person who did not set it up can follow it.
CBackup’s own cloud to cloud backup walkthrough covers the mechanics of creating one of these jobs; the retention question is the one to raise with the vendor before you retire any other copy.
AOMEI vs CBackup: Decision Matrix
| Attribute | AOMEI Backupper Standard | CBackup |
|---|---|---|
| Free tier | 0 USD Standard edition for a single Windows PC; several disaster-recovery features are paid | 10GB CBackup space plus 50GB public-cloud transfer |
| Paid entry point | Professional from 39 USD.95; Workstation from 49 USD.95 | Basic at 4 USD.99/month or 29 USD.94/year; Premium at 14 USD.99/month or 89 USD.94/year |
| Operating system | Windows 11 / 10 / 8.1 / 8 / 7 | Windows only |
| Primary job | System, disk, partition, and file images to local, NAS, or cloud targets | Cloud file backup, cloud-to-cloud copy, and quota pooling |
| Backup speed | Paid editions read data from the hard drive faster than Standard, and paid differential backup cuts the time a repeat job takes | No speed tiers or throttling stated across the free, Basic, and Premium plans |
| Bare-metal recovery | Yes for the same hardware; dissimilar hardware needs paid Universal Restore | Not documented by CBackup |
| Encryption evidence | No backup-archive encryption standard stated for the free edition | Vendor claim of 256-bit AES |
| Scheduling | Daily, weekly, monthly, plus event- and USB-triggered jobs | One-time, daily, weekly, monthly |
| Fleet management | PXE boot and image deployment tools appear in paid editions | Not documented by CBackup |
| Best fit | Endpoint image with a local or NAS recovery target | Documents already living in supported cloud accounts |
| Watch out for | Universal Restore, differential backup, and cleanup sitting behind the paywall | Quota ceiling on the free plan; no documented imaging or retention guarantee |
Which Office Should Choose Which
One to five Windows PCs, a NAS in the back room, no server admin
Choose AOMEI Backupper Standard. You need the machine back, not just the files. Build the WinPE media on day one, schedule a weekly system image to the NAS, and accept that recovery onto a different laptop model will need the paid upgrade. Trade-off: someone has to delete old images manually on the free tier.
Critical files already in Google Drive, OneDrive, or Dropbox
Choose CBackup. The data is already off-site; what you lack is a scheduled, provider-independent copy. Pool two or three accounts, run a daily job, and test a restore in week one. Trade-off: the included space disappears fast, so budget for Basic once the archive outgrows a document share.
Both problems in the same office
Run both tools for different jobs. AOMEI images the endpoints; CBackup copies the documents and the shared drives. Two workflows mean two sets of credentials, two schedules, and two restore tests on the calendar. That overhead is smaller than rebuilding a machine from scratch.
Ten seats, a line-of-business database, or a recovery-time target
Neither free tier, yet. Verify commercial licensing, get a written answer on VSS and application-aware backup, and price the edition that includes dissimilar-hardware restore and central deployment. Treat free as a proof of concept here; production needs the paid edition.
Business-Readiness Checklist
Before you install either tier on a company PC
- The EULA permits commercial use on the number of machines you plan to install
- A backup ran while a file was open and locked, and the restored copy opened cleanly
- If imaging is part of your plan, a full system image was restored to a spare disk and booted
- Encryption settings and passphrase custody are documented, with a copy held offline
- If you pool cloud accounts, the combined quota is written down, with each provider’s contribution and terms
- Where the tool offers version retention or deletion recovery, it is confirmed in writing, or an archive covers the gap
- The paid tier that closes your remaining gap has been priced and approved
- A restore test is on the calendar for next quarter, with a named owner
The Verdict
Recovery capability settles the choice. Start with the failure that would stop the office tomorrow, install the tool that shortens it, and put the upgrade on the budget line for the quarter you can afford it. A Windows office that cannot lose a machine needs WinPE media built on day one and a weekly system image landing on the NAS. An office whose working documents already live in the cloud needs two or three accounts pooled behind one daily job, with the quota total written down. Running both costs an extra schedule and an extra set of credentials, which is cheaper than rebuilding a laptop from scratch.
Deployment comes before trust. Switch encryption on in the client, store the passphrase offline, record the quota arithmetic, and restore one file and one image before the first month ends. Then put a restore test on the calendar each quarter with a named owner, and keep the result in writing. A backup job that has never been restored is an assumption with a progress bar.
💬 Comments