Skip to content

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

Backup & Restore

The Backup and Restore sections of EMCP Tools → Safety → Backup & Migrate package your site into a single portable .emcp archive and restore it. Both run from your browser in short, resumable slices, so large sites finish reliably on modest hosts. Keep the tab open while a manual backup or restore runs. You can switch to another section of the screen meanwhile; the job keeps going.

  1. Open EMCP Tools → Safety → Backup & Migrate. The Backup section opens by default (&view=backup).
  2. Under What to include, choose:
    • Full site: database and all files (uploads, themes and plugins). Since 3.21.0 the site’s root wp-config.php is left out: it holds the database password and secret keys, and a restore never writes it, because the destination keeps its own.
    • Database only: posts, pages, settings and users, no files.
    • Files only: uploads, themes and plugins, no database.
  3. Optionally give it a Backup name (for example “Before plugin update”). A timestamp is used if you leave it blank.
  4. Click Start backup. Progress is shown live, with a Cancel button while it runs.
  5. The finished archive appears in Your backups (the newest six) and in the History section (all of them), with its type, size, status and date. Use Download to save the .emcp off-site.

EMCP Tools → Backup & Migrate → Backup section, with the Create a backup form, the Backup health card, the EMCP Cloud card and the Your backups table

Since 3.20.0 backups are kept where the web server cannot hand them out. Before 3.20.0 they sat in wp-content/emcp-backups/ behind an .htaccess deny, which nginx hosts ignore, so anyone who knew a backup’s address could download it. EMCP now picks the folder in this order:

  1. EMCP_BACKUP_DIR: set this constant in wp-config.php to a folder path and every backup goes there.
  2. Outside the web root: a new folder next to the WordPress folder, chosen only when that parent folder is writable, lies outside the document root and does not look like a web root itself (no index.php, .htaccess, web.config or wp-config.php in it, and not named public_html, www, htdocs and similar). This matters on addon domains and subfolder installs, where the parent is another site’s web root.
  3. Inside wp-content: otherwise, wp-content/emcp-backups- followed by 20 characters derived from the site’s secret keys in wp-config.php. The name cannot be guessed, and it stays the same after a database restore.

Every time EMCP uses the folder it puts back its .htaccess (Apache 2.2 and 2.4), web.config (IIS) and index files. Backups from the old wp-content/emcp-backups/ folder move over automatically, never while a backup or restore is running.

Once a week EMCP writes a test file into the folder and fetches it over HTTP. If the web server serves it, the Dashboard’s Needs your attention list shows “Backups can be downloaded from the web” and the Storage card gives an nginx rule that blocks the folder. Block it, or set EMCP_BACKUP_DIR to a folder outside the web root.

The Storage card on the History section shows the backup folder and how it was chosen, the result of the web check (with Check again), and the disk space backups use.

Under Retention:

  • Keep manual and AI backups (1 to 100, default 10): backups made by hand or by an AI agent beyond this number are deleted, oldest first. Scheduled backups follow the Keep the newest number in their own schedule.
  • Size limit (GB) (0 means no limit): the oldest completed backups of any kind are deleted until the rest fit. The newest backup is always kept.

The limits apply after every backup, when you save them, and once a day. The same daily cleanup removes failed partial backups, restore uploads nobody is using and other leftovers once they are more than a day old.

New in 3.18.0. The Backup health card on the Backup section shows the date of the Last backup (or “Never”), the current Schedule, and a warning when there is no backup yet or none in the last 14 days.

  1. Click Set up (or Edit once a schedule exists) next to Schedule. The Scheduled backups drawer opens.
  2. Turn on Run scheduled backups.
  3. Choose the Frequency (Daily or Weekly) and the Time, in the site’s time zone.
  4. Choose What to include: Full site (database and files), Database only, or Files only.
  5. Set Keep the newest (1 to 30, default 7). Older scheduled backups are deleted when a new one finishes. This number never touches manual or AI backups, which follow the retention limits.
  6. Click Save schedule.

Scheduled backups run through WP-Cron in short ticks, so they need some site traffic (or a system cron) to keep moving. The Backup health card warns “Scheduled backups aren’t running” when DISABLE_WP_CRON is set and no scheduled backup ran recently, and flags a scheduled backup that has not moved for two hours. On a site with DISABLE_WP_CRON, call wp-cron.php from a system cron every few minutes. A failed scheduled backup is retried a few times before it is marked failed, and the Dashboard’s Needs your attention list then shows “The last scheduled backup failed”.

When you open the Backup section while a scheduled backup is running, the notice “A scheduled backup is running.” shows its progress, read-only. If the backup has stopped moving (usually because WP-Cron has not run), the notice says so and offers Continue in this tab: click it to drive the rest of the backup from your browser, like a manual one. Only one process works on a backup at a time, so a backup you continue here is never processed twice.

The Restore section (&view=restore) restores archives that are in the upload folder, the uploads folder inside your backup folder. The Restore section prints its exact path. There are two ways to get an archive there: upload it in the browser, or copy it in by FTP. To restore one of this site’s own backups, download it from Your backups first, then upload it here.

  1. On the Restore section, click Drop an .emcp file or choose one (or drag the file onto the drop zone).
  2. The uploader sends it in chunks and adapts to your host. If a chunk is rejected it automatically retries with a smaller one, so it works even behind a firewall or a strict request-size cap. Real progress drives the bar, and an interrupted upload resumes.
  3. When the upload finishes the archive appears in Available to restore.
  1. In Available to restore, choose the archive (the radio button in the first column).
  2. Tick Restore database, Restore files, or both.
  3. Click Restore selected, type RESTORE to confirm, and keep the tab open. The plugin imports the database, extracts files, and rewrites URLs to this site.

Remove uploaded files deletes every archive in the upload folder once you no longer need them.

The reliable method for very large sites: FTP drop

Section titled “The reliable method for very large sites: FTP drop”

For very large archives, or any host that fights browser uploads, skip the uploader:

  1. Copy the .emcp file into the upload folder shown on the Restore section (the uploads folder inside your backup folder) via FTP/SFTP or your host’s file manager.
  2. It appears in Available to restore on the Restore section with no browser upload at all.
  3. Restore it the same day: the daily cleanup deletes files in that folder that are more than a day old and not in use by a restore.

This has no size limit and bypasses every request-size cap. See Server upload limits for the details.

EMCP Tools → Backup & Migrate → Restore section, with the "Restoring overwrites this site" warning, the Upload a backup drop zone and the Server upload limits table

A restore:

  • Imports the database and rewrites the site address and Elementor page-data URLs to this site (a serialization-safe search-replace, so serialized data and Elementor JSON stay valid).
  • Extracts the archived files into place.

A restore never:

  • Modifies wp-config.php or your security salts.
  • Logs you out. Your current session is preserved even though the database is replaced mid-restore.

A connected agent can create and list backups with the create-backup and list-backups MCP tools (both on by default). Backups it creates are stored on this server like any other. See the module overview.