
A WordPress backup is only complete when it covers two components: the database and the files. Neither is useful without the other. The database holds every post, page, option, user, and comment. The files hold the theme, plugins, and uploaded media.
Files: WordPress core, wp-content/themes, wp-content/plugins, wp-content/uploads, wp-config.php. Database: the single MySQL database containing all posts, settings, and user data.
The most common mistake is backing up only the database and forgetting about wp-content/uploads, which can be gigabytes of media files that are never included in a plain database export.
For non-technical users or shared hosting environments, WordPress plugins handle backup scheduling directly from wp-admin. The main options:
Plugin backups have one important limitation: they rely on WP-Cron, which only fires when someone visits the site. A low-traffic site may miss scheduled backups for days. For production sites, combine plugin-based backups with server-level scheduling.
On a VPS, you can back up WordPress directly from the command line without any plugin involved — more reliable and faster for large sites:
The --single-transaction flag on mysqldump ensures a consistent snapshot without locking the database — critical for live sites. The --exclude flag skips the cache directory, which can be large and is always regeneratable.
Backup frequency should match how often your data changes:
CloudStick's Backups section handles both website files and database backups from a single dashboard view — no SSH required, no cron to configure, no scripts to write. Enable backup per-website or per-database, choose your schedule and retention period, and CloudStick stores the archives in its managed backup storage.
See the CloudStick knowledge base: How to Enable Database Backup for step-by-step instructions on enabling database backup for each WordPress site from the CloudStick dashboard.


We use cookies to improve your experience
CloudStick uses cookies to personalise content, analyse traffic and keep you signed in. Cookie Policy · Terms of Service