Your prompt

Set up daily database backups and weekly full backups for my site, stored off the server, keeping 14 days of history. Then show me how to restore one.

What this prompt does

This prompt sets up a backup routine with two rhythms: the database every day and a complete copy of the site every week. The copies are stored off the server, and the last 14 days are kept. It also asks your AI assistant to show you how to restore one.

Off-server storage matters because a backup kept on the same machine can disappear with it. The restore demonstration is just as important, because a backup you have never restored is an untested assumption.

The assistant will usually do this by installing or configuring a backup plugin, and what it can do depends on the plugin chosen.

If your host already keeps its own copies, this routine is a second, independent safety net that you control rather than a replacement.

Before you run it

  • Choose where backups go: a cloud storage account, a separate server or another provider. Have the login ready.
  • Make sure that storage has enough room for 14 days of history, since full copies of a large media library add up.
  • Check whether your host already provides backups, so you do not double up needlessly.
  • Ask which plugin the assistant plans to use and what it will cost.

Setting up backups is not risky for your content, but the schedule can slow a small server while it runs, so pick a quiet hour.

What to check afterwards

  • A first backup has run, and appears in the off-server location.
  • The schedule shows daily database and weekly full jobs.
  • Retention is set to 14 days and old copies are removed.
  • You have seen the restore steps and, ideally, tried one on a staging site.
  • You receive an alert if a backup fails.

Ways to adapt it

  • Change the cadence: Run database backups every six hours because I publish all day.
  • Extend retention: Keep 30 days of history and one monthly copy.
  • Choose the location: Store backups in my cloud storage account, not on the server.

If it goes wrong

  • Backups fail on a large site. Exclude cache folders, or ask the host to raise time and memory limits.
  • Storage fills up. Shorten retention or exclude large, easily replaced folders.
  • The restore does not work. Test on a staging copy and confirm both the files and the database were included.

The best backup plugins compares tools, and building a backup routine covers the habits around them.

← Every prompt on WPMusk

SponsoredNibWP

Stop clicking. Start telling.

Ask your AI to build pages, fix speed and nail SEO, and NibWP does it on your WordPress site in minutes.

Try NibWP.com

Get the WPMusk Sunday brief

One email a week with our newest tutorials, honest tool reviews and resources you won’t find on the blog. No spam, unsubscribe in one click.

Newsletter (Sunday brief)