Skip to content
dvnt.io

Resources · glossary

Backup

A copy of data and files kept separately from the live service, from which you can restore everything after a failure, a break-in or a simple mistake. A backup that has never been restored is an assumption, not protection.

Also called
  • backup
  • data backup
  • website backup
  • backup and restore
  1. 01

    Three questions that decide its quality

    How often it is made, how long it is kept and how long a restore takes. The answers decide how much work you lose on your worst day, and that is the only number that matters in this conversation.

  2. 02

    Why one copy is not enough

    A copy on the same server dies with it, and a copy overwritten every day will not help if you notice the problem a week later. A sensible setup is at least one place off the server and several points in time.

  3. 03

    The test almost nobody runs

    A trial restore. Only that shows whether the backup covers the database together with the files, whether someone other than one person has the passwords to it, and how long it really takes. Without this test you have a procedure, not protection.

  4. 04

    What it costs

    Less than people usually assume. Storage is cheap, and most of the cost is setting it up once and checking it regularly. In the maintenance calculator, backups are one of the items you can switch on to see the difference.

In practice

Related terms

  • Website maintenanceOngoing care of a live website: hosting, updates, backups, monitoring and small content changes. A cost you pay every month, whether or not anyone included it in the implementation quote.
  • SLA (service level agreement)A written commitment from the provider on availability and response time: what counts as an outage, how quickly someone will deal with it, and what happens if they fail to.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.