What this problem looks like
A complete WordPress backup has two parts: the MySQL database and the wp-content directory plus core files you customized. Missing either half makes restore impossible or incomplete.
Manual backups complement plugin schedulers. Run one before major changes even when your host promises daily snapshots.
Export the database in phpMyAdmin
- Open hosting → phpMyAdmin.
- Select the WordPress database.
- Click Export → Quick → SQL → Go.
- Save the .sql file with the site name and date in the filename.
Export with WP-CLI
cd /path/to/wordpress
wp db export ~/backups/mysite-$(date +%F).sql
wp db export --tables=wp_posts,wp_postmeta ~/backups/posts-only.sql
Download files via SFTP
Connect with SFTP and download wp-content/ entirely. Include uploads, plugins, and themes.
Also save wp-config.php from the site root and .htaccess if present.
- Large uploads folders may take hours. Compress in file manager when available.
- Exclude cache folders inside wp-content/cache if space is tight.
- Note WordPress core can be re-downloaded but custom core edits need saving.
What a backup plugin adds
Plugins like UpdraftPlus bundle database and files into one archive on a schedule. Manual steps still matter when the plugin itself is broken or the site is down.
Storage and retention
Keep at least three restore points: before updates, before migrations, and a recent weekly copy.
Store backups off the web server. Ransomware and host failures can destroy local copies.
When to stop DIY and hire help
If manual backups feel slow or you need tested daily restores, BugShield Shield maintenance includes cloud backups and restore help from UK developers.