Definition: Sauvegarde
Copy of data used to restore a website, database or service after an incident.
In web infrastructure, this term should be understood in relation to domain names, active services, security and continuity. A poor configuration may affect the website, email or access to services.
Practical checks
- Identify where the configuration is managed.
- Keep a record of important changes.
- Test the effect of a change before considering it complete.
- Document dependencies with the website, email or backups.
Why this term matters
This term is often connected to several other technical elements. For example, a DNS change can affect the website, email, SSL certificates, message delivery or the availability of a service.
Before modifying a configuration, identify the responsible provider, keep the previous value, note the time of change and plan validation after propagation or after restarting the relevant service.
- Verify where the configuration is managed.
- Keep a record of the previous state.
- Test the result with more than one tool when possible.
- Document the potential impact on the website, email or access.
Frequently asked questions
Is this important for a small website?
Yes. Even a small website often depends on DNS, SSL, email and backups.
Should this configuration be documented?
Yes. Simple documentation reduces risk during migration or incidents.