Skip to main content
Cookbook Maintenance Duplicator

Back up your site before a plugin update with AI

Have your AI take a full Duplicator backup, confirm it finished, and only then update the plugin.

Difficulty Beginner
Time ~10 min

Prerequisites

A connected site running Duplicator 5.0.2 or newer on WordPress 6.9 or newer. Enough disk space on the host for a full backup archive.

The prompt
I use Duplicator on my WordPress site and I want to update the [plugin name] plugin safely. Do this in strict order. First, use the Duplicator abilities to start a full site backup (scope "all") with the reason "Before updating [plugin name]". Then poll the backup status every 20 seconds until it reaches a terminal state. Do not do anything else while it runs. If the status is failed, cancelled, or missing, stop, tell me the message Duplicator returned, and do not update the plugin. If the status is complete, tell me the backup id, whether it is a full backup, any exclusions listed, and give me the link to its details page. Only after you have shown me a complete backup, update the [plugin name] plugin and confirm the version it is on now. If anything about the update needs my approval, ask before you proceed. End with two lines: the backup that protects this change, and the version the plugin moved from and to.
Already connected?

Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:

Run the “Back up your site before a plugin update with AI” recipe from the WPVibe cookbook on my connected site.

A plugin update is the most common change that breaks a WordPress site, and the backup before it is the most commonly skipped step. Not because anyone disagrees with it. Because the update button is right there, and the backup is on a different screen, with a progress bar you have to wait for. So the update goes in first and the backup stays a good intention.

The AI puts the two in order. It starts a full Duplicator backup with the reason written on it, polls the status until Duplicator reports it complete, reads back the size and whether anything was excluded, and refuses to touch the plugin until that is true. Then it runs the update through WordPress’s own updater and confirms the new version. If the backup fails, the update does not happen and you get told why.

Paste the prompt with the plugin’s name filled in. A full backup of a large site can take several minutes and needs room on disk, so if Duplicator warns about space, sort that out first. The AI can create backups but cannot restore one; restoring stays in the Duplicator dashboard, and the status report gives the AI the link to the right page so it can hand you a direct route there.

Outcome

A completed, full-site Duplicator backup named for the update, and the plugin updated only after the backup reported complete.