A usable website backup normally includes both files and the matching database. Back up before updates, migrations, bulk content changes, or DNS cutovers.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Choose the right scope: Use a full-account backup for disaster recovery or separate file and database exports for a single site.
- Create a consistent copy: For busy applications, use maintenance mode or a tool that coordinates database and file snapshots.
- Download off-server: Keep at least one encrypted copy outside the hosting account so a server or account incident cannot remove every backup.
- Label and retain: Record the site, creation time, application version, and retention date. Protect backups as sensitive data.
- Verify integrity: Confirm archives open and database exports contain tables; periodically perform a test restore to staging.
Important notes
- A backup stored only on the same hosting account is not sufficient disaster recovery.
- Do not publish backup archives inside the website’s document root.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
