Logon
Nederlands, English
Donate to ASK-Solutions (the IRADIS Foundation)

Make, test and restore a backup

Make, test and restore a backup

A backup strategy does not start with a particular NAS brand or software package. First determine which data needs protection, how quickly it changes and how much downtime is acceptable.

Then choose layers and test recovery. The test is essential: restoring is where missing databases, passwords, symlinks, permissions or keys become visible.

Backups often contain the most sensitive information. Access control and encryption therefore belong in the same design.

Questions on this page

What should I include in the backup?

Not only documents. Think about mail archives, website files and databases, bookkeeping, configuration, exports, photos, certificates and data on phones or a NAS. Start with an inventory for each system.

How often should I back up?

Base this on how much work you can afford to lose. Data that changes daily needs a different frequency from a photo archive that is updated once a month. Also consider retention periods and version history.

How do I protect backups against ransomware?

Make sure not every backup remains permanently writable with the same permissions. Offline, immutable or separated storage can help. Also test that recovery accounts and keys do not exist only on the compromised system.

How do I carry out a restore test?

Choose a representative set of files and, at least occasionally, a complete application. Restore to a separate location, check content and permissions and document the steps required. Only then do you know whether the procedure is usable.

Practical testing can be done through Digital.