The best backup software is the one you actually use

Anyone looking at backup software for Windows will quickly come across impressive feature lists: block-level increments, deduplication, Linux hardened repositories, central management consoles. All technically clean, all well thought out. And yet I've been experiencing the same pattern for years: data backup doesn't fail because of the technology, it fails because it was never set up properly!

That sounds banal. But it isn't. Because the decision for a backup solution is usually not made in the IT department of a company. It is made at the desk of a craftsman's business, in the accounts department of an architect's office or on the home PC of a freelancer. And it is not the architecture that determines the protection of the data - but the question of whether the backup runs reliably at all.

Enterprise thinking meets SME reality

Let's take a concrete example. Veeam is an excellent backup solution. The engine is powerful, the increments efficient, the administration well thought out for large environments. If you want to back up a VMware or Hyper-V cluster with dozens of virtual machines, you will hardly find anything better.

But now the crucial question: How many of my readers operate such a cluster?

The reality for the vast majority looks like this: A Windows PC or a small network. Maybe a NAS in the basement. An external hard disk. Maybe a cloud storage. No Linux server, no dedicated backup administrator, no budget for infrastructure that only exists for data backup.

And it is precisely in this reality that something surprising happens: Without a Linux hardened repository - i.e. without a hardened Linux server as a backup target - even a powerful enterprise tool loses a large part of its security advantage. Because the best protection against ransomware is useless if it assumes that you can administer Linux.

Data backup under Windows: my clear idea of it after 20 years of Langmeier backup development

Over the years, I have developed a pretty clear idea of what 80 to 90 percent of all Windows users actually need:

• An image backup of the entire system, so that not only the data but also the operating system can be restored in an emergency
• A file backup for quick access to individual documents without having to restore the entire image
• A simple restore that also works under stress - ideally hardware-independent
• Versioning, so that you not only have the latest version, but can also access older versions
• Less complexity during setup and maintenance
• The ability to restore individual files directly from an image backup

This is not wishful thinking. This is what makes the difference between "data saved" and "everything lost" in an emergency.

Ransomware protection is not an optional feature, it's a MUST

Now it's getting serious. Ransomware is the single biggest threat to data today. And protection against it is not a checkbox in a piece of software. It is a strategy.

Two concepts are crucial here, and both are feasible for everyone:

Airgap: the physical separation of data

The principle: after the backup, the data carrier is physically separated. No network, no access, no risk.

In concrete terms, this means

• Backup to an external hard disk
• Remove after the backup
• Ideally, use two data carriers alternately

This is not high-tech. It's common sense. And it is one of the most effective protection mechanisms of all - because what is not connected cannot be encrypted.

Immutable storage - unchangeable backups

The following applies to cloud backup: data must not only be stored, but must still be available unchanged after an attack. This is exactly what immutable storage is for - so-called WORM (Write Once, Read Many).

With a cloud connection that supports WORM and defined retention periods, backups are protected against

• Encryption by ransomware
• Accidental or intentional deletion
• Manipulation through compromised access data

The combination of both - local Airgap plus cloud with immutable storage - results in a data protection strategy that meets professional enterprise standards without enterprise complexity.

Veeam vs. Langmeier Backup as Windows backup software

I could draw up a feature table now. But I won't. Instead, I'll give you an honest classification of when which solution makes sense.

Enterprise backup solutions like Veeam are the right choice when:

• Dozens or hundreds of systems are managed centrally
• A dedicated IT team looks after the infrastructure
• Linux server expertise is available in-house
• The environment is primarily virtualized
• Budget is available for specialized backup infrastructure

A Windows-native solution such as Langmeier Backup is more suitable if:

• One to fifty Windows workstations are to be backed up
• No Linux know-how is available
• The setup should work quickly and without external help
• External hard disks, NAS and cloud are sufficient as backup targets
• Individual files are to be restored directly from image backups
• The solution should run easily on a day-to-day basis, without constant support

Both approaches are justified: if you have server and Linux knowledge, you can use the extended immutable backup strategies in Veeam. But if you want to back up your data quickly and easily under Windows without having to set up a Linux server first, Langmeier Backup is the right tool for you.

Changing the backup media and using multiple backup media ensures a physical separation (airgap) between the devices and the backed-up media and offers good protection against ransomware.

SME data backup: a concrete best-practice setup

For all those who want to know what a solid data backup for a small or medium-sized company can look like in practice, here is a tried-and-tested setup:

Daily backup with air-gap (physical separation):

• To an external USB hard disk or an external USB SSD disk
• Incremental, so that only changes are backed up (automatically in Langmeier Backup)
• Enable versioning of important file types and folders (e.g. *.docx)

After each backup:

• The external hard disk is first virtually disconnected
• A sound after the backup informs the user to change the external backup hard disk to ensure a physical separation (airgap) to the data.
• Use a second hard disk alternately

Additionally:

• Daily automatic NAS backup
• Cloud backup with immutable storage (WORM), e.g. the Langmeier Backup Immutable Cloud Storage or aBusiness Suite.
• or alternatively: Mirror NAS to a second NAS at another location via RSYNC.

What this setup covers:

• Hardware failure → Image restore to new hardware
• User error → Restore individual files from versioning
• Ransomware → Airgap backup is not affected
• Fire or theft → Cloud backup in another location
• Total loss → Hardware-independent recovery from the cloud

This setup does not require a server. No IT specialist. No knowledge of Linux. It requires two external hard disks, a cloud connection and ten minutes to set up.

What to do if several computers are to be backed up on site?

If several computers are to be backed up on site, a single central workstation PC is defined. All other computers back up their files to this central workstation PC via a network share.

The person at the central workstation PC is responsible for the backup to external media and creates the physical separation (airgap).

Windows backup: Why the built-in solution is not enough

A question I often hear: Isn't Windows' own backup enough? The short answer: For a basic backup yes, for real protection no.

Windows' on-board tools offer neither reliable image backups with hardware-independent recovery, nor versioning over longer periods of time, nor meaningful cloud integration. And experience shows: Restoring via Windows' own tools is error-prone and cumbersome in an emergency.

If you take your data seriously, you need dedicated backup software. Which one depends on your own scenario - but "none at all" is the worst option.

What counts in the end

I have been involved in many restores in my career. The most painful ones were not the ones where the technology failed. They were the ones where there was no usable backup at all. Because the setup was too complicated. Because the external hard disk hadn't been connected for months. Because no one had ever tested whether the restore worked.

A theoretically perfect backup that is never set up does not protect anyone. A simple backup that runs daily and is then physically disconnected saves data. Every day, reliably, without ifs and buts.

Good data backup is not a question of maximum complexity. It is a question of good habits. And the right software for your situation.

It's not the most complex backup that wins - but the one that reliably restores data in an emergency.