Two backups can both report “completed” every night and give you very different mornings after a failure. One returns your documents. The other returns the whole machine, with its operating system, programs and settings already in place.
That is the difference between a file backup and an image backup. Neither one is better in general. Each fits a different kind of machine, and most small businesses need both, pointed at different things.
What a file backup copies
A file backup copies the files and folders you choose: documents, spreadsheets, drawings, scans, exported app data. A good one keeps versions, so you can pick a file as it was at 10 a.m. yesterday rather than only as it is now.
Restoring is quick and precise. You choose a folder and a point in time, and it comes back. For the most common problem in any office, a deleted or overwritten file, this is the right tool.
What a file backup does not hold is the machine itself. The operating system, installed programs, drivers, license activations, scheduled tasks and the many small settings that make a server behave are not in it. If the whole machine fails, you have the contents of the house and still need to build the house.
What an image backup copies
An image backup copies a whole disk or volume, block by block. That includes the operating system, every installed program, the configuration, the data and the information the machine needs to start. After the first full image, later images usually send only the blocks that changed, so a nightly image of a large server does not mean sending the whole disk every night.
The restore is the point. An image can be written back to the same hardware, to replacement hardware (often called a bare-metal restore) or into a virtual machine. The server comes back as it was at the moment of the image, ready to start.
Images have costs too:
- Size: an image includes everything, so it takes more storage than the data alone.
- Rhythm: images usually run once a night, not every hour.
- Hardware: restoring onto very different hardware can need extra driver work.
- Single files: you can pull one file out of an image, but it is slower than a file restore.
Where each one fits
A useful rule: image the machines that would take more than a day to rebuild by hand, and use file backup for the rest.
| System | Better fit | Why |
|---|---|---|
| Laptops and desktops | File backup | The work lives in a few folders, and a new laptop can be set up from a standard build |
| File server | Image plus file versions | The shares, the permissions and the server itself all matter |
| Accounting or line-of-business server | Image plus file versions | Reinstalling the app and its database by hand can take days |
| NAS shares | File backup of the shares | The NAS system is simple to reset; the shared folders are what matter |
| Microsoft 365 or Google Workspace | Neither: an app-level backup | Mail, sites and drives are copied through the service’s own interfaces |
Laptops are the case people argue about. Imaging a laptop sounds thorough, but an image of a 500 GB drive is slow to send from a home connection and slower to restore. Most of what matters on a laptop sits in the user’s folders. That is why the Workstation Backup plan copies file changes every hour the laptop is online, keeps 90 days of versions, and takes full-disk images only when a client asks for them.
The exception is the odd workstation that runs software you cannot easily reinstall: a machine that drives lab equipment, a production line or a plotter with a fussy driver. Treat that one like a server and image it.
Servers are the opposite case. A server carries years of setup that nobody wrote down. The Server Backup plan takes a nightly image at 11 p.m. and hourly file versions through the day, so you can rebuild the machine from the image and then bring the files forward to within the hour.
How the restore differs
Picture the same failed server restored two ways.
With file backup only, the work runs in this order: get hardware, install the operating system, apply updates, reinstall each program, find the license keys, restore the database, recreate shares and permissions, fix mapped drives on every PC, then restore the files. Each step is simple. Together they take a day at best, and often longer, because some of them wait on a software vendor’s support line.
With an image, the order is shorter: restore the image to working hardware or a virtual machine, start it, check the apps, then restore any file versions newer than the image. The setup comes back in one step because it was copied in one step.
The recovery time you can actually hit depends on which of these two paths your backup supports. If you have not yet agreed how long each system can be down, recovery point and recovery time, explained covers the idea in a few minutes.
Example: a bad update on a property office server
Take a 35-person property management company. One Windows server runs its leasing and maintenance software and also holds the shared drive, about 400 GB in all. An automatic update installs at 3 a.m. on a Friday, and the server will not start when the first staff arrive at 8 a.m.
With file backup only. The documents are safe. The leasing software is not: it has to be reinstalled from the vendor’s installer, licensed again and pointed at a restored copy of its database. Shares and permissions are rebuilt from memory. The office spends Friday on paper and in the vendor’s queue, and the realistic target is Monday.
With an image and hourly versions. The 11 p.m. Thursday image was taken before the update ran. It is written back to the same hardware, which is healthy, and the office’s IT contact pauses that update until it has been tested. Nobody worked between 11 p.m. and 3 a.m., so there are no newer file versions to replay. For a server of this size, that is a matter of hours rather than days, though the exact time depends on disk speed and hardware.
The lesson is not that images are better. The image saved the setup, and the hourly file versions would have saved the day’s work if the failure had come at 4 p.m. instead. A server needs both.
Check your own backups
Use these questions to see what you have today:
- Which machines would take more than a day to rebuild by hand? Those need an image.
- Does your server backup include the operating system and programs, or only the data folders?
- How often do file versions run between images?
- Can an image restore to different hardware, or into a virtual machine?
- Do laptops back up from home and on the road, or only on the office network?
- Where do images go: only a local disk, or also to a copy outside the building?
- When did someone last restore a whole machine, not just a file?
The last question matters most. An image that has never been started is a hope with a file size. How to test a restore without breaking anything walks through doing it safely, and the Restore Drill plan restores one full system every quarter and sends the result in writing.
Words you will see on quotes
Backup quotes use a handful of terms for these ideas. Bare-metal restore means rebuilding a machine from an image onto empty hardware. Incremental means copying only what changed since the last backup. System state means the settings Windows needs to run a server as itself. If a quote uses a term you do not recognize, the backup and recovery glossary defines it in a line or two.
A calm next step
If you are not sure which of your machines are imaged and which only have their files copied, that is a normal place to start. The free backup check takes 45 minutes, remotely: we look at what runs today, try one test restore, and send a written page of what we found. You can book a free backup check whenever it suits you.
