Backup strategy: backups that can actually be restored when it matters.

A daily backup is quick to set up. What counts is whether it works when something goes wrong. We check this regularly and define how long your data is kept.

Server fronts with drive bays

From backup to tested restore

A backup is only worth something once restoring it has been proven to work.

  1. Set upThe database is backed up every day.
  2. Define retentionWe draw up a retention plan in line with GoBD (German rules for digital bookkeeping).
  3. Test the restoreWe regularly check that the backup can actually be restored. We agree the schedule with you.
  4. DocumentSetup and checks are documented, so every step is clear when something goes wrong.

What the backup is needed for

A backup strategy has to fit the cases that can actually happen.

Deleted by mistake
Someone deletes records, or a faulty update overwrites them. Then you need a version from before the error.
The server fails
The disk is broken, or the system no longer starts. The backup must also restore onto new hardware.
Malware on the network
If ransomware reaches the backup too, the backup is worthless. A copy that is disconnected from the network or kept off site is spared.
Old data is needed
Tax-relevant data must be kept in a traceable way. The retention plan in line with GoBD defines which versions are kept and for how long.

Key terms in brief

  • 3-2-1 ruleThree copies of your data on two different types of storage, one of them off site. If one storage device or one location fails, a copy remains.
  • Full and incremental backupA full backup contains everything; an incremental one only the changes since the last backup. That saves time and space, but restoring needs the whole chain.
  • Consistent backupSimply copying the files of a running database often produces an unusable backup. The reliable route is the database's own tools.
  • Transaction logMany databases log every change. Together with a full backup, this lets you restore the state at a specific point in time.
  • Recovery objectivesHow much data can you afford to lose at most, and how long may the outage last? These two answers determine how often and how you back up.
  • Restore testThe backup is restored as a test and checked. Only then is it clear that it is complete and how long recovery takes.

Kept under watch with a maintenance contract

With a maintenance contract, we monitor backups, updates and antivirus for a fixed monthly fee and act before things break. This applies to the database as much as to the rest of your IT.

Maintenance contracts in IT support

Frequently asked questions

Is a daily backup enough?

That depends on how much data you can afford to lose. With a daily backup, you lose up to one day in the worst case. If that is too much, the transaction log lets you restore a later state.

Which databases do you set up backups for?

We work with MySQL and MariaDB, Microsoft SQL Server and MongoDB.

Why does the restore need testing?

A backup can run without errors for a long time and still be incomplete, for example because a new database was not included. Only a test shows this.

What if the data is already lost?

Deleted by mistake, a system crash or a failed disk: we recover data, and the initial diagnosis is free of charge. More under repair and data recovery.

When did you last restore your backup?

We check your data backup and set it up so it holds when it matters.

0173 644 22 17
Discuss a database project