A useful backup must contain enough data to restore the service, not merely a copy of a few website files. For dynamic sites this normally means files plus databases; email may also need separate protection.
Step by step
- Before updates, migrations or destructive changes, take a fresh backup.
- For a CMS, back up the document root and export its database.
- Keep at least one backup outside the same hosting account so a full account failure does not remove both live data and backup.
- Label backups with the domain and date and periodically remove obsolete copies that consume disk space.
- Test restoration procedures on non-production data where practical.
Important
Backups are only valuable if they can be restored. Do not assume an automated backup exists unless you can see the backup service or HostLaunch has confirmed the retention policy.
Checks and troubleshooting
If you need a restore, identify the desired date and exactly what needs restoring: files, database, email or the full account. Restoring old data can overwrite newer changes.