Solid Backups plugin review and common issues

Large site backup timeouts are a common issue on shared hosting. Solutions: (1) in Solid Backups → Settings → Advanced Settings, enable “JavaScript chunking” which breaks the backup into smaller pieces to avoid PHP timeout; (2) enable “Backup only on schedule” and schedule during off-peak hours when server resources are more available; (3) create separate backup profiles for database-only (fast) and files-only (can be scheduled separately); (4) exclude large, non-essential directories (cache, log files, large media not needed for backup) in the backup exclusion settings; (5) consider upgrading hosting to a managed VPS where PHP limits can be increased.

Google Drive upload failures typically involve authentication or quota issues: (1) in Solid Backups → Destinations → Google Drive, click “Test” to verify the connection is current — OAuth tokens expire; (2) re-authenticate the Google Drive connection by disconnecting and reconnecting with your Google account; (3) verify the Google Drive account has sufficient storage for the backup file; (4) check if the backup file size exceeds Google Drive API’s chunk upload limits (for very large files); (5) a network timeout between the WordPress server and Google’s API can interrupt the upload — retry from the backup list.

ImportBuddy performs database search-replace to update URLs to the new domain/path. If URLs are still pointing to the old site: (1) in the ImportBuddy restoration wizard, verify the old URL and new URL are correctly entered for search-replace; (2) some URLs may be stored in serialized data that requires format-aware search-replace — ImportBuddy handles this, but verify no missed serialized values with a separate Better Search Replace check; (3) clear all caches after restoration; (4) if the search-replace step was skipped, run Better Search Replace manually with old URL → new URL targeting all database tables.

Solid Backups’ real-time database backups trigger a database backup when specific WordPress actions occur — including WooCommerce order creation. In Solid Backups → Settings → Real-time Backups, enable database backups triggered by WooCommerce order events (woocommerce_new_order, woocommerce_order_status_changed). Each order triggers a database backup, ensuring order data is immediately preserved. Balance this with storage considerations — high-volume stores can generate many backups. Configure remote storage for real-time backups to avoid filling local server storage.

Create a full-site backup using Solid Backups on the source site. Download the backup ZIP file to your computer. On the new hosting environment, create a blank WordPress installation. Upload the ImportBuddy PHP file (downloadable from the Solid Backups admin) to the new site’s root directory. Upload the backup ZIP to the same directory. Access ImportBuddy via browser (yourdomain.com/importbuddy.php). Follow the wizard: enter the backup ZIP path, configure the database credentials for the new host, update the new domain URL. ImportBuddy extracts files, restores the database, and performs URL replacement.

UpdraftPlus free covers the core backup needs (scheduled backups to Dropbox/Google Drive/S3) at zero cost, making it the better value for most WordPress sites. Solid Backups’ advantages are: BackupBuddy Stash cloud storage included in the license (no separate cloud storage account needed), ImportBuddy’s standalone restoration without a working WordPress, and a decade-plus reliability track record. For sites where disaster recovery without a functioning WordPress is a specific concern, or for agencies that prefer a single-vendor backup solution with included cloud storage, Solid Backups justifies its cost over UpdraftPlus free.

BackupBuddy Stash is SolidWP’s own cloud backup storage service. Solid Backups licenses include a limited amount of Stash storage (historically 1GB, check current license terms). Additional Stash storage can be purchased separately. Stash provides a backup storage destination without needing a separate Google Drive, Dropbox, or S3 account — useful for users who want a contained backup solution. For sites with large backups or requiring extensive backup history, the included storage may be insufficient and additional Stash storage or an alternative like S3 may be more economical.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.