How to Back Up WordPress by Plesk WP Toolkit

admin

4 hours ago

How to Back Up WordPress by Plesk WP Toolkit backup tutorial showing files database offsite storage and restore verification

How to Back Up WordPress by Plesk WP Toolkit is for Plesk users, agencies, and hosting providers who want a per-site WordPress backup without backing up the whole subscription. Use this method when individual WordPress backups before core, plugin, theme, or staging changes.

A good WordPress backup includes the website files and the database. The files carry themes, plugins, uploads, configuration, and custom code. The database carries posts, pages, users, settings, WooCommerce orders, booking records, form entries, menus, and plugin data. Before you change WordPress core, PHP, DNS, plugins, themes, checkout, or a page builder, make sure you know which backup contains both halves.

When this backup method makes sense

Plesk WP Toolkit is a good fit when you already have that tool available and need a practical restore path. It is especially useful before updates, redesign work, hosting migrations, malware cleanup, PHP changes, database work, and plugin troubleshooting.

Before you begin

Confirm the WordPress URL and document root so you back up the right site.
Find the database name in wp-config.php or the hosting panel.
Check free disk space; many backup failures start with a full account.
Pause risky work until the backup finishes and you can see the file.
For stores and booking sites, note the last order, booking, or form entry before the backup.

Backup steps

Log in to Plesk and go to WordPress.
Open the card for the target WordPress installation.
Click Back up / Restore, then click Back up.
Wait for the backup to appear in the WP Toolkit backups list.
Download the backup file if you need an off-server copy.
Label the maintenance ticket with the backup time before making changes.

Automated backups and cron

Plesk WP Toolkit backups are convenient per-site safety copies. For recurring protection, combine them with Plesk Backup Manager scheduled backups or another offsite backup system.

For WordPress plugin backups, remember that WordPress scheduled tasks often depend on WP-Cron. WP-Cron runs when WordPress receives traffic and notices a task is due. That is fine for many small sites, but low-traffic sites can run late. For business-critical sites, pair plugin schedules with a real server cron, hosting-panel backups, or provider backups where available.

How to test restore readiness

Use Back up / Restore on the same installation card and choose the restore icon for the backup. Plesk warns that restoring can remove changes made after that backup date, so capture the current state first when possible.

Do not test your only restore for the first time during an outage. Use a staging copy, temporary subdomain, local development environment, or provider restore preview when available. After restore, check login, home page, important pages, media, forms, checkout, email delivery, permalinks, and cache behavior.

Common mistakes

Assuming a WP Toolkit backup covers every site in the subscription.
Leaving the only backup in the site account forever.
Restoring without warning store owners that orders or form submissions after the backup time may disappear.
Forgetting to test wp-cron if scheduled maintenance jobs stop running.

Where to store the backup

Keep at least one copy outside the web server. Good destinations include your own Google Drive, Dropbox, OneDrive, S3-compatible storage, Backblaze B2, Wasabi, SFTP, a provider backup vault, or a secure internal backup server. The exact tool matters less than the restore test, retention policy, and separation from the production account.

Fix I.T. Phill recommendation

Use Plesk WP Toolkit as one layer, not the whole plan. Keep a second backup path for important sites, especially WooCommerce, bookings, memberships, and agency-managed sites. Before major updates, take a fresh manual backup even if automatic backups are already scheduled.