←  All terms
B
Hosting & Infrastructure

Backup

A backup is a separately stored copy of data or system state used to restore information after loss or failure.

A backup is a separately stored copy of data or system state used to restore information after loss or failure. A robust setup considers availability, security, scalability, observability, and a tested recovery path. The concept is closely related to Managed Hosting and Rollback.

Read more

Managed Hosting

Rollback

Resilience

Deployment

FAQ

Backup

Is the hosting provider's backup sufficient?
A hosting provider's backup usually protects against platform failures, not necessarily against mistakes in day-to-day operations. Retention, scope, and restore time vary by contract. For business-critical content, an independent backup of its own makes sense unless the contract offers suitable commitments.
Why does a backup need to be tested regularly?
A backup counts as reliable only once a restoration has been rehearsed successfully. Test runs should happen regularly and after infrastructure changes. Restores often fail because of missing credentials, corrupted files, or unclear responsibilities, not because of the copying itself.
How does a backup differ from a rollback?
A rollback returns an application to an earlier code version, while a backup restores data such as databases or uploads. After a faulty deployment, a rollback is usually enough. After data loss or tampering, only a backup leads back. Both belong in a recovery concept.
What does the 3-2-1 rule mean for backups?
The 3-2-1 rule calls for three copies of the data on two different storage media, with one kept at a different location. That way backups survive device failure, operator error, and site damage. For websites, it means not keeping all copies with the same provider and in the same account.