Saved database copies

In “Database”, saved copies let the project owner return to earlier production data. This tool appears after database setup finishes.

Saving a copy

1. 1

   Open saved copies

   In “Database”, wait for readiness and find the saved copies section.

2. 2

   Label the copy

   Click “Save a copy now”. Enter an optional description of up to 80 characters, such as “Before updating products”.

3. 3

   Save and wait

   Click “Save” and wait for the confirmation and dated entry. Completion time varies. On an error, review the message and list before retrying.

Restoring production data

1. 1

   Review the copy you need

   Choose the copy by its description and date. Review data added to the live website since that date before replacing it.

2. 2

   Open the restore confirmation

   Click “Restore” beside it. A notice explains that current data will be replaced and an automatic copy will be saved first. You can cancel at this point.

3. 3

   Confirm and wait

   If you intend to proceed, confirm the restore. Wait for the result; it can take minutes. Avoid repeating the request while restoration is in progress.

4. 4

   Check the live data

   Open the published website and check its data and key features. The app’s database connection remains managed without copying a new URL. On an error or missing result, review the list and website state before retrying or contacting support.

Copy limits and deletion

You can keep at most 6 manual copies. Automatic copies may be cleaned up by later operations, so they are not a permanent archive. Save a clearly named manual copy when you need a specific recovery point.

1. 1

   Review what you are removing

   Choose an old copy you no longer need. Deleting it removes that recovery point.

2. 2

   Use the trash icon

   Click the delete-copy icon. Deletion starts immediately without a second confirmation. Wait for the entry to disappear or an error to appear.

3. 3

   Handle limits or dependencies

   At the limit, remove an unneeded copy and save again. If deletion is refused because a copy supports a previous restore, follow the message to remove an unneeded newer copy first, or contact support.