RSN Site Backup Pro creates compressed backups of your entire WordPress site - the\ndatabase and every file - and stores them wherever you want. Restoring is a single\nclick and works even when moving the site to a new domain or host.<\/p>\n\n
All three are available, and a scheduled backup can be mirrored to as many of\nthem as you like. A backup you start yourself from the Backup Now<\/strong> screen\nalways goes to the one destination you pick there.<\/p>\n\n Following the standard WordPress backup\/restore principle, a package contains:<\/p>\n\n Under Settings -> Backup contents<\/em> you choose what the file archive covers:<\/p>\n\n The backup storage folder, cache folders and While a backup or restore is running, the progress card offers three controls:<\/p>\n\n A stopped job keeps its slot, so a new backup cannot start until it is resumed\nor cancelled. If a job is stopped and then abandoned for 24 hours, it is\ncancelled automatically so it can never block future backups.<\/p>\n\n Because the work happens on the server, a stopped job stays stopped even if the\nbrowser is closed - WP-Cron leaves it alone until you press Resume.<\/p>\n\n Every selected destination is verified before<\/em> the backup starts. If FTP is\nmissing its host, username or password, or Google Drive has not been connected,\nthe backup is refused straight away with a message naming the problem, rather\nthan building a large package and failing at upload time. All problems are\nlisted at once so they can be fixed in a single pass.<\/p>\n\n On the Backup Now<\/strong> screen you pick exactly one destination - the three\nchoices are radio buttons, so only one can ever be selected and one is always\nchosen for you. If you pick a destination that is not set up yet, the backup\nstops before it starts and tells you what is missing.<\/p>\n\n Scheduled backups work differently: under Settings<\/em> you can tick several\ndestinations, and every scheduled run is mirrored to all of them.<\/p>\n\n The restore screen follows the correct order so a moved site just works:<\/p>\n\n You can restore the database, the files, or both, and choose a different site\naddress in the same step.<\/p>\n\n Google Drive needs your own OAuth client, because only then are the backups\nyours alone. Creating one is a one-off, and takes a few minutes:<\/p>\n\n If you would rather type the values yourself, use the Enter them by hand\ninstead<\/em> link.<\/p>\n\n Google ends a connection for a few reasons, and the plugin names which one\napplies:<\/p>\n\n Temporary problems - the site being offline, Google being briefly unavailable -\nare never treated as a dead connection, so a network blip will not cost you a\nworking setup.<\/p>\n\n Replacing your credentials also disconnects the account, because a stored\nconnection only ever works with the client that issued it. The plugin does this\nfor you and tells you to reconnect, rather than leaving a connection that looks\nfine and then fails during an overnight backup.<\/p>\n\n RSN Site Backup Pro does not send backups, analytics, or other site data to RSN.\nIt only contacts external services that an administrator explicitly configures:<\/p>\n\n The plugin stores the destination settings and Google OAuth credentials in this\nWordPress installation. Site owners should update their site's privacy policy\nto explain their chosen backup destination and the data contained in backups.<\/p>\n\n\n For Google Drive, see Connecting Google Drive<\/em> below.<\/p>\n\n\n No. The plugin runs entirely inside WordPress. The local destination works on\nany host, including shared hosting.<\/p><\/dd>\n No. Backups and restores are broken into short slices, each saved to the\ndatabase and resumed by the next request or by WP-Cron.<\/p><\/dd>\n Yes. Create a backup, then restore it on the destination with the new address\nfilled in. Every stored URL, including serialised data, is updated for you.<\/p><\/dd>\n Inside Yes. Archive entries are validated before extraction, and any path containing\n ..\/ or an absolute path is rejected.<\/p><\/dd>\n No. Stopping and resuming are handled entirely on the server, so a job stays\nstopped between browser sessions and continues from the same point when you\npress Resume.<\/p><\/dd>\n\n<\/dl>\n\n\nHow a backup works<\/h4>\n\n
\n
database.sql<\/code> - a full dump of every table, with a manifest of the source site.<\/li>\nfiles.zip<\/code> - the site files (see Backup scope<\/em> below).<\/li>\nwp-config.php<\/code> - included for reference so you can see the source site's\nconfiguration. The plugin never writes it to the site root; on a new host,\nrun the WordPress installer first so it creates its own wp-config.php.<\/li>\nrsn-backup-manifest.json<\/code> - site URL, paths, table prefix and format version.<\/li>\n<\/ul>\n\nBackup scope<\/h4>\n\n
\n
wp-content<\/code> is backed up: uploads, plugins and themes.\nSmaller and much faster, which is all most recoveries need.<\/li>\nwp-admin<\/code>, wp-includes<\/code>, wp-content<\/code>, wp-config.php<\/code> and every\nother file sitting at the top level. Use this for a complete, self-contained\ncopy that can rebuild the site from scratch on a new host.<\/li>\n<\/ul>\n\nnode_modules<\/code> are always skipped,\nso a backup can never include itself. The setting screen shows the current scope\nand the file count\/size it will produce.<\/p>\n\nStop, resume and cancel<\/h4>\n\n
\n
Connection checks before backing up<\/h4>\n\n
Choosing a destination<\/h4>\n\n
Seamless restore<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
Connecting Google Drive<\/h3>\n\n
\n
\"Google no longer accepts this connection\"<\/h4>\n\n
\n
Third-party services and privacy<\/h3>\n\n
\n
\n
rsn-site-backup-pro<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Do I need FTP or SSH access?<\/h3><\/dt>\n
Will a large site time out?<\/h3><\/dt>\n
Can I move my site to a new domain?<\/h3><\/dt>\n
Where are backups stored locally?<\/h3><\/dt>\n
wp-content\/rsn-backups<\/code> by default. The folder is protected with an\n index.php guard and an .htaccess<\/code> deny rule.<\/p><\/dd>\nIs my data safe during extraction?<\/h3><\/dt>\n
Will a stopped backup be lost if I close the browser?<\/h3><\/dt>\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
invalid_grant<\/code>.<\/li>\n1.0.0<\/h4>\n\n
\n