Backups, Restore Points and Remote Backup

1. Understand what the backup system is

The hosting platform maintains backup copies independently of your live files. In GreatHosts CP you can browse multiple dated restore points and initiate restoration yourself.

2. Do not infer a fixed retention schedule

The visible account shows many restore points, including closely spaced recent versions and older versions. However, schedules/retention can differ by service and platform policy. Treat the dates shown in your account as the source of truth.

3. Restore deliberately

Before restoring, identify whether you need a single file, website files or a wider account state. Record the current state first when possible so recovery does not erase a newer valid change.

• Confirm the restore point timestamp.
• Understand what scope the Restore action covers.
• After restoration, test the site and database-dependent functions.
• If the problem is uncertain, contact support before overwriting a working state.

4. Use remote backup for another copy

GreatHosts CP supports remote backup workflows to Google Drive and Dropbox. An independent destination is useful for critical projects because it separates one copy from the hosting account itself.

5. Back up before risky changes

Take or verify a usable restore point before major CMS updates, migrations, bulk database changes, theme/plugin replacements or deployment of a large new release.

6. A backup is not validated until restore is possible

For important sites, periodically confirm that you can locate the expected data and understand the restore workflow. A backup label alone is not enough if nobody knows what it contains or how to recover it.

7. Keep application-level exports when useful

For databases or applications with their own export functions, an additional logical export can complement platform backups and make selective recovery easier.

Services related to this guide