@@PRODUCT@@

Making and downloading restore points of applications

Before every update CoreCP makes a restore point of your application by itself: a copy of the files and the database, with a way back if the update breaks something. You can also make one yourself, whenever you want — before you try a new t

Written for: Customer, Reseller, Administrator

Before every update CoreCP makes a restore point of your application by itself: a copy of the files and the database, with a way back if the update breaks something. You can also make one yourself, whenever you want — before you try a new theme, before a big clean-up in your forum, or simply because you want a copy on your own computer. It works for every application in the catalogue, not only for WordPress.

Making a restore point

Open Applications, click the application and choose Make a restore point. Give it a name you will recognise later, for example "before the new design", and a date until which you want to keep it. Leave the date empty and it is kept for 30 days; longer than a year is not possible. A restore point is not an archive: the full history of your site is in your account's backups.

The restore point appears on the History tab, with its name, the moment it was made and the date until which it is kept. Once that date has passed, CoreCP tidies it away at night.

How many, and what it costs

You keep at most three restore points you made yourself per application at a time. If you want a fourth, first delete an old one with Delete next to it. The restore points CoreCP makes for an update do not count towards that: of those, the last five are kept, and they never push your own restore points out.

A restore point you made counts towards your account's disk space. It is a full copy, so a 200 MB site costs 200 MB extra for as long as the restore point exists. If it no longer fits in your disk space, CoreCP tells you before anything is stored. The restore points CoreCP makes itself do not count.

WordPress works exactly the same way. A restore point you make on the WordPress screen and one you make under Applications are two of the same kind and count together towards the three.

Downloading

Next to every restore point is Download. Your browser then fetches one archive with two things in it: the folder files/ with all of the application's files, and database.sql.gz with the complete database. With those you can rebuild the site somewhere else, or simply keep it.

The link behind the button works once and for 24 hours. If the download does not start, or breaks off, just click Download again: that makes a new link. Only you — and your hosting provider or administrator — can download a restore point of your site. Nobody can look into where the restore points are stored: not even your own account can, because the database holds the password codes of every user of your site.

Putting it back

Choose Put back next to the restore point. Your site's files and database then go back to that moment. Everything that changed on your site since — new posts, orders, comments — is gone afterwards. If you are in doubt, download the restore point first, so you have both versions.

From the restore screen: safer, and from any backup

Under Backups, the restore screen has an Applications tab. It puts an application back from one of these restore points or from a backup of your account, with two things the button on the card does not do:

  • the site as it is now is kept first as a restore point (seven days), and is put back by itself when the restore fails part-way;
  • you can choose Beside it, as a new website: the moment comes back on hersteld-<date>.<your website> and your live site stays as it is.

How it works step by step is in Your own backups § Restoring an application.

From the terminal

If you prefer the command line, you have the same options:

$ corectl app snapshot phpbb:example.nl/forum --label "before the clean-up" --keep-until 2026-12-31
$ corectl app snapshots --instance phpbb:example.nl/forum
$ corectl app snapshot-download <restore-point> --instance phpbb:example.nl/forum
$ corectl app snapshot-remove <restore-point> --instance phpbb:example.nl/forum

See also Removing an application: before an application is removed, CoreCP first makes a restore point of it.