How to Back Up WordPress by Kinsta

admin

4 hours ago

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

How to Back Up WordPress by Kinsta is for Kinsta customers, agencies, ecommerce teams, and developers using staging and production environments. Use this method when managed WordPress restore points, hourly backup add-ons, downloadable backups, and staging restore tests.

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

Kinsta MyKinsta backups 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

Open MyKinsta and select the WordPress site.
Go to Backups and review daily, hourly, manual, system-generated, or downloadable options available on the plan.
Create a manual backup before plugin updates, PHP changes, search-replace work, or staging pushes.
Download a backup when you need a portable copy of files and database.
Use staging for restore testing when possible.
Record the backup type and retention window in the maintenance notes.

Automated backups and cron

Kinsta creates managed backups automatically, and hourly backups are available as an add-on for sites that change constantly.

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

Restore from MyKinsta to the intended environment. For non-standard WordPress structures, read Kinsta notes carefully before assuming a database password or path will be updated automatically.

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 daily backups are enough for a busy store.
Not buying hourly backups when order volume requires them.
Restoring to live instead of staging.
Not keeping a downloadable copy before high-risk migrations.

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 Kinsta MyKinsta backups 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.