Your own server
Packages land in wp-content/rsn-backups, ready to download any time.
- Works on any host, including shared hosting
- Guarded by
index.phpand an.htaccessdeny rule - Instant restores with nothing to re-download
RSN Site Backup Pro creates compressed packages of your database, files and configuration — then stores them on your server, an FTP server or your own Google Drive. Migrate to a new domain or host without touching a single file by hand.
Manual backups go to the one destination you pick. Scheduled backups mirror to all the destinations you tick — so an off-site copy exists automatically.
Packages land in wp-content/rsn-backups, ready to download any time.
index.php and an .htaccess deny ruleUpload to any FTP host, with optional TLS, passive mode and a custom path.
Backups go to your own Drive account through Google's OAuth2 flow — nobody else's.
Every selected destination is tested before the backup starts — you find out about a missing FTP password now, not at 3 a.m. mid-upload.
Long jobs run in short server-side slices that are saved and picked up again by the next request or by WP-Cron — so you can close the browser and the backup carries on.
Local, FTP or Google Drive. Nothing else to configure — no server access, no SSH keys, no cron jobs to write by hand.
Back up now, or set a schedule from hourly to monthly with a start time. Scheduled runs mirror to every destination you enabled.
Choose a backup, optionally enter a new address, press Restore. Database, URLs and files all land in the right order.
A single self-contained archive following the standard WordPress backup principle — enough to rebuild the site from scratch on a brand new host.
database.sqlA full dump of every table, generated in resumable
batches.
files.zipYour site files — wp-content by default, or the
entire root on request.
wp-config.phpSo a new host can be rebuilt from the package
alone.
rsn-backup-manifest.jsonSite URL, paths, table prefix and format
version.
Under Settings → Backup contents:
Uploads, plugins and themes. Smaller and much faster — all most recoveries need.
wp-admin,
wp-includes, wp-content, wp-config.php and every top-level file.
The backup folder, cache folders and node_modules are always skipped, so a backup can never
include itself.
Built for real sites: shared hosting, large databases, migrations, and people who need a restorable copy without thinking about it.
Hourly, twice daily, daily, weekly or monthly, with a start time you choose. WP-Cron keeps working even when nobody has the admin open.
Pause a job and it keeps its exact state — the dump continues from the table it stopped on, not from zero. Abandoned jobs clear themselves after 24 hours.
Optional encryption for packages at rest, so a package sitting on a destination is never readable without your key.
Keep the last N backups and/or everything newer than a set age. Old packages are pruned automatically — storage never creeps up on you.
Every run records what it did, per backup. When something goes wrong you can read the reason instead of guessing.
Script backups and restores from the command line, or wire them into your own deploy and maintenance routines.
Restores run in the correct order, so a site that lands on a new domain or new host simply works — serialised data included.
../ or an absolute path is rejected.
No. The plugin runs entirely inside WordPress. The local destination works on any host, including shared hosting, and remote destinations are configured through their own credentials.
No. Backups and restores are broken into short slices, each saved to the database and resumed by the next request or by WP-Cron — so a multi-gigabyte site finishes without ever hitting a PHP timeout.
Yes. Create a backup, then restore it on the destination with the new address filled in. Every stored URL — including serialised data — is updated for you, so the site works at its new address.
Inside wp-content/rsn-backups by default. The folder is protected with an
index.php guard and an .htaccess deny rule, and the path can be
changed in Settings.
Yes. Archive entries are validated before extraction, and any path containing ../
or an absolute path is rejected outright.
No. Stopping and resuming happen entirely on the server. A stopped job stays stopped between sessions and continues from the exact point it reached when you press Resume.
Never. RSN Site Backup Pro sends no backups, analytics or site data to us. It only contacts the services you explicitly configure — Google Drive and your own FTP server.
Install it, choose a destination, and your first full backup is running in under a minute — no configuration files, no server access required.
WordPress 5.6 – 7.1.x · PHP 7.4+ · GPL-2.0-or-later · Version 1.1.1