CaryvaneHelp
/
EN

WordPress backup

Most WordPress sites live on shared or managed hosting, where the host's own backups stay with the host, last days or weeks, and come back through a support ticket. Caryvane backs up each site's files and its whole database every night into the customer's own storage, keeping every snapshot for as long as you choose. The site only needs a small plugin, which can read the site but never change or delete anything.

What the plugin can and cannot do

The Caryvane Backup plugin answers only requests signed by Caryvane for that site; anything else gets the same "not found" as a missing page. It can list and read files and read database tables. It has no way to change, upload or delete anything, it never writes backups to the web server, and it holds no key that opens anything in Caryvane. The backups are written straight to the customer's storage by Caryvane, so a hacked site cannot reach or damage them.

1. Install the plugin on the site #

  1. In the Caryvane console: Connectors → choose the customer → in the WordPress card, Add a site. The dialog shows a connection key and a Download the plugin link.
  2. In the site's WordPress admin: Plugins → Add New → Upload Plugin, choose the downloaded caryvane-backup.zip, Install Now, then Activate. An administrator account is needed.
  3. Settings → Caryvane Backup: paste the connection key and click Connect to Caryvane.

The key works once and expires after 30 minutes; if it runs out, New key on the site's row issues another. The plugin connects only to Caryvane's own servers: a key that points anywhere else is refused, so nobody can talk an administrator into sending the site to someone else.

The console notices the site connect within a few seconds, checks that it can read it, and opens the site's settings.

2. Choose where it is backed up, and where the backup runs #

Saving starts the first backup straight away.

3. What is captured #

Always left out: caches (wp-content/cache, the caches of common caching plugins, and WP-CLI's download cache .wp-cli/cache), other backup plugins' archives (UpdraftPlus, All-in-One WP Migration, Duplicator and similar), node_modules, .git, and log files over 50 MB.

How it reads the site: a little at a time, in short requests that fit inside shared hosting's limits, at most two at once and backing off when the host is busy. The first backup copies everything and a large site may take a few nights to finish; it carries on where it stopped each time. After that each run reads only the files whose size or date changed, and only the parts of each table that changed. Content that is identical across snapshots is stored once.

The database is read while the site is live, so a snapshot is a careful copy taken over a few minutes rather than one instant. The busiest tables (settings, sessions, orders) are read last and checked again before the snapshot closes, and anything that changed meanwhile is read again.

4. Snapshots #

Connectors → WordPress → Snapshots lists every snapshot with its date, size and how much changed. Open one to walk its folders, download any single file exactly as it was, and see its database tables with row counts and the plugins and themes installed that day.

Snapshots older than the retention period are removed, and with them anything no remaining snapshot needs. The newest snapshot is always kept.

5. Getting a site back #

Download this snapshot (in the snapshot view, or the download_wordpress_snapshot assistant tool) writes three files into a new, dated folder of the site's storage. Nothing on the live site changes.

FileWhat it is
files.zipThe site's files as they were. wp-config.php kept above the site folder is in _above-site-root/.
database.sql.gzThe whole database as a MySQL dump that phpMyAdmin, the mysql client or WP-CLI imports.
README.txtThe snapshot's details and the steps below.
  1. Upload the contents of files.zip to the site's folder on the host (or a new host).
  2. Create an empty database, or empty the existing one, and import database.sql.gz.
  3. Check the database name, user and password in wp-config.php match the host's database.
  4. Moving to a different address? Change it with a tool that understands WordPress's stored data, for example wp search-replace 'https://old' 'https://new'; a plain text replace breaks it.

A single file (a deleted image, a theme file before an edit) needs no download: open the snapshot and download that file.

6. What it costs #

In Caryvane's cloud a WordPress site is an ordinary cloud job: one cloud credit for each day its backup runs (however many times that day), plus the data transferred above your allowance. How often it runs therefore decides the cost. On one of your agents it uses that agent and no cloud credits. See Billing & trial; ask us for current rates. WordPress backup is not available on a trial.

Troubleshooting #