Backups & reliability · practical answers
What should a Linux backup setup include?
Scope and starting price
Choose the relevant service below. We confirm the systems covered, checks and final price before work begins. Additional work and third-party costs need to be included in the agreed quote.
Linux Backup
From £79
An agreed automated Linux backup configuration with a defined restore check.
Backups & Recovery servicesWebsite / Database Backup
From £99
A backup approach for the named website or database and its agreed recovery path.
Backups & Recovery servicesAutomated Backup Scheduling
From £99
Set up the agreed backup schedule and identify how failed jobs will be noticed.
Backups & Recovery servicesDecide what must be recoverable
List the files and services needed to resume work. For a server, this may include application files, database contents and configuration. Identify anything stored outside the machine, such as a hosted database, before assuming one backup job covers the whole service.
Agree how recent a recovered copy needs to be and how long older versions should remain available. These decisions affect storage, scheduling and cost; they should be made around the business need rather than a default chosen without discussion.
Keep recovery copies protected
The NCSC advises making backups of essential information, knowing how to restore it, and protecting backup access. It also warns that removable backup media left connected can be affected by an infected computer.
Choose storage and access arrangements that suit your system. An external drive, a remote location or a managed storage service may be appropriate, with hardware and recurring storage charges made clear in the quote.
Technical reference: NCSC: backing up your organisation's data
Finish with a restore path
Agree a test that restores selected material to an appropriate separate location and checks it can be used. Record what was recovered, from which copy, and which parts of the system were outside that test.
The handover should identify the schedule, destination, retention approach and recovery steps. Also agree who checks failed jobs and when the arrangement should be reviewed after changes to the system.
Is this the right fit?
A good fit when
- A Linux workstation or server holds information that would be difficult to replace.
- You want to set up or replace a defined backup process.
Limits of the scope
- The starting price does not include storage hardware, cloud subscriptions or unlimited data.
- A new backup setup does not recover information already lost or prove every application can be rebuilt.
What to prepare for an enquiry
- The systems and data to protect, approximate size and expected growth.
- Existing backup destinations and whether any recent restore has been attempted.
- How much recent work you could afford to lose and who should own routine checks.
Start with a description and non-sensitive examples. Leave out passwords, API keys, private keys, recovery codes and customer data. Access arrangements are agreed separately if the work needs them.
Common questions
Is synchronising a folder enough?
Check what happens after deletion, corruption or unwanted changes, and whether older independent copies can be recovered. The backup scope should make those recovery cases explicit.
Can this include a database?
Yes, website and database backup is a listed service. Name the database and application so a suitable backup and restore procedure can be included in the quote.
Will backups be checked after setup?
An initial restore check belongs in the agreed setup. Continuing checks, reporting and maintenance need a named owner or a separate ongoing arrangement.
Related answers
Backups & reliability
How can I tell whether my backups will restore?
Backups & reliability
What should a small-business disaster recovery plan contain?
Linux infrastructure