How to Back Up WordPress by InfiniteWP

admin

4 hours ago

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

How to Back Up WordPress by InfiniteWP is for admins and agencies already managing sites through an InfiniteWP panel. Use this method when self-hosted management workflows, backup jobs before updates, and repository-based offsite storage when the add-on is available.

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

InfiniteWP 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

Add the WordPress site to InfiniteWP and confirm the child connection works.
Open Backups for the selected site.
Choose whether the backup includes files, database, or both.
Run a manual backup before updates or destructive work.
Configure repository/offsite backup support if your InfiniteWP setup includes it.
Download or verify the backup location and record the restore point in the maintenance ticket.

Automated backups and cron

InfiniteWP can schedule backup jobs depending on the installed features and add-ons. Monitor the panel because failed child connections can quietly stop useful backups.

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 InfiniteWP or the repository destination. Confirm the target URL and site before restoring, especially when several client sites are in the same management panel.

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

Not securing the InfiniteWP admin panel.
Backing up to the same server as the managed site only.
Ignoring failed child-site connections.
Not separating agency dashboard backups from client-site backups.

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 InfiniteWP 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.