Take a database backup before bulk edits with AI
Get a fast database-only Duplicator backup before your AI rewrites a batch of posts, changes settings, or runs a search and replace.
Prerequisites
A connected site running Duplicator 5.0.2 or newer on WordPress 6.9 or newer. Use this before content, settings, or search-and-replace work; it does not cover files.
I use Duplicator on my WordPress site. Before I ask you to [describe the bulk job, for example rewrite the meta descriptions on all posts in the Guides category], take a database-only backup. Use the Duplicator abilities: start a backup with scope "database" and the reason "Before [short name for the job]". Poll the backup status every 15 seconds until it is complete, failed, cancelled, or missing. If it did not complete, tell me Duplicator's message and stop; do not start the bulk work. If it completed, tell me the backup id, quote the exclusions Duplicator lists so I know exactly what this backup does not cover, and give me the link to its details page. Then stop and wait. Do not begin the bulk job until I reply with "go".
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Take a database backup before bulk edits with AI” recipe from the WPVibe cookbook on my connected site.
Most of what an AI changes on a WordPress site lives in the database. Post content, meta descriptions, options, menus, a search and replace across a hundred URLs. A full site backup before each of those is the careful move, but on a big site it takes minutes and a chunk of disk, so it gets skipped for anything that feels small. Sixty rewritten posts do not feel small afterwards.
Duplicator can take a database-only backup, and the AI can ask for one. It starts the backup with the job named as the reason, waits for Duplicator to report it complete, and reads back the exclusions so you hear, in Duplicator’s own words, that site files are not included. On the test site it took under a minute. Then it stops and asks you to say go on the bulk work, so the backup is in place before the first edit and not after.
Paste the prompt with the job described in a few words, then give the bulk work as your next message once the backup is confirmed. A database backup does not protect theme files, plugin files, or uploads, so if the job touches any of those, use the full backup recipe instead. Restoring a backup is still done from the Duplicator dashboard; the AI can take one but cannot put it back.
Outcome
A completed database-only backup, named for the job you are about to do, and a clear note from the AI that files are not in it.