Backups, Schedules and Recovery

Prepare the destination and choose what to copy

Where to find: Integration → Cloud Storage; Instant Backups; Schedule Backups

Application backup is not a complete image of the server. Choose the scope according to the data you need to recover.

1. Link a destination in Integration → Cloud Storage.
2. Identify the application and the database actually used by the project.
3. Choose the copy type: File System, Application or Database.
4. Set formats, retention and frequency as required by the project.
5. After generating a first copy, check the files and plan a separate environment recovery test.

Understand the fields and options

File System

Copies only the files from the chosen application. It does not automatically include the database.

Application

Copy files and selected database. Check both source fields.

Database

Just copy the chosen database.

.tar / .tar.gz

Pack of uncompressed files/compressed package with gzip.

.sql / .sql.gz

Dump SQL without compression / compressed SQL dump. They are not MongoDB backup formats.

Retention Period

Duration of maintenance of copies, different from the frequency of execution.

Create an Instant Backup

Where to find: Instant Backups → Create

Use an immediate copy before updating the site or changing data. Quick Backup, on the Dashboard of the application, also offers a shortcut to this form.

1. Open Instant Backups → Create.
2. Inform Backup Name with a useful identification, such as before-update shop.
3. Choose Backup Type. For an application copy, check out File Type and Database File Type.
4. Select Application and Database according to the chosen type. Do not assume that any listed database belongs to the project.
5. Select Storage Provider and Retention Period.
6. Review source, destination, and scope and click Create an Instant Backup.
7. Open Instant Backups → Backups and check the status, date and project. Wait for completion before the change that depends on the copy.

Create a routine of scheduled backups

Where to find: Schedule Backups → Create

The frequency defines when to run; the retention defines how long to store copies. Set both.

1. Open Schedule Backups → Create.
2. Choose Backup Type, formats and origins Application and Database.
3. Select Storage Provider and Retention Period.
4. In Schedule, choose the frequency presented by the panel.
5. Keep Start immediately after creation marked if you want to start after saving. To schedule the start, uncheck and fill Start From with the date and time.
6. Check the time zone used by the scheduler before setting times. Do not automatically convert a UTC time as if it were Brasilia time.
7. Click Create a Schedule and check out the routine in Schedules.
8. After execution, open Schedule Backups → Backups and confirm the generated copy.

See routines, copies and archived files

Where to find it: Schedule Backups → Schedules / Backups; Instant Backups → Backups; Archive Backups

Use the appropriate list to find what you are looking for. An empty screen can also be the result of filters.

1. In Schedules, check out Storage, Application, Database, Schedule, Retention Period, Status, Total Backups, Last Backup At and Next Backup At.
2. In the instant and scheduled copy lists, select Type, Application, Database, and Date Range.
3. Apply the filter and check name/project, provider, status, type and Created At. Use the filter cleaning action if a copy does not appear.
4. In Archive Backups, select Application, File System or Database and order Created At in ascending or descending order.
5. Use the Actions column of the completed copy to see the operations actually offered.
6. Regularly review last execution, next execution and storage result.

If the result is not expected

Prepare download and restore safely

Where to find: Copy list → Actions

Recovery must use the correct copy, with compatible scope and destination. Data created after copying can be replaced.

1. Choose copy per application, database, type, date and status completed.
2. Before restoring, preserve the recent state and plan the unavailability and data saving window.
3. Open the copy actions. If there is Download, store the file in a protected location and check its size and format.
4. If the panel offers Restore, review origin, destination, components and replacement notices before confirming.
5. Wait for the result and test files, pages, login, database, uploads and integrations.
6. If the necessary action is not available, gather type, date and location of the copy for service. Do not improvise an import in production.

Plan an application copy or migration

Where to find: Application → Site Clone; backup lists

Use Site Clone for the copy stream offered by the application. The observed form did not display selector from another server; confirm this availability before planning a transfer.

1. Prepare a recoverable backup of the source.
2. Check out technologies, runtime version and database at desired destination.
3. See the Clone Site tab to create a copy with new name, domain, and database when this stream meets the goal.
4. Test the copy before changing the DNS.
5. Check out SSL, uploads, cronjobs, supervisors and external integrations.
6. Plan the DNS exchange and avoid divergent recordings between origin and destination during the transition.