RSN Site Backup Pro

Description

RSN Site Backup Pro creates compressed backups of your entire WordPress site – the
database and every file – and stores them wherever you want. Restoring is a single
click and works even when moving the site to a new domain or host.

Destinations

• Local computer / server – keeps packages on your web server so you can
  download them to your computer at any time.
• Remote server (FTP / FTPS) – uploads to any FTP host, with optional TLS.
• Google Drive – stores backups in your own Drive account using Google’s
  OAuth2 flow, including resumable uploads for large files.

All three are available, and a scheduled backup can be mirrored to as many of
them as you like. A backup you start yourself from the Backup Now screen
always goes to the one destination you pick there.

How a backup works

Following the standard WordPress backup/restore principle, a package contains:

• database.sql – a full dump of every table, with a manifest of the source site.
• files.zip – the site files (see Backup scope below).
• wp-config.php – included for reference so you can see the source site’s
  configuration. The plugin never writes it to the site root; on a new host,
  run the WordPress installer first so it creates its own wp-config.php.
• rsn-backup-manifest.json – site URL, paths, table prefix and format version.

Backup scope

Under Settings -> Backup contents you choose what the file archive covers:

• Off (default) – only wp-content is backed up: uploads, plugins and themes.
  Smaller and much faster, which is all most recoveries need.
• On – “Include all files in the root folder of the site” archives the whole
  install: wp-admin, wp-includes, wp-content, wp-config.php and every
  other file sitting at the top level. Use this for a complete, self-contained
  copy that can rebuild the site from scratch on a new host.

The backup storage folder, cache folders and node_modules are always skipped,
so a backup can never include itself. The setting screen shows the current scope
and the file count/size it will produce.

Stop, resume and cancel

While a backup or restore is running, the progress card offers three controls:

• Stop – pauses the job and keeps its state exactly where it is.
• Resume – continues from that point; the database dump restarts at the
  table it stopped on rather than from the beginning.
• Cancel – discards the job and its partial files. A cancelled backup is
  listed with a cancelled status and can be deleted from the Backups screen.

A stopped job keeps its slot, so a new backup cannot start until it is resumed
or cancelled. If a job is stopped and then abandoned for 24 hours, it is
cancelled automatically so it can never block future backups.

Because the work happens on the server, a stopped job stays stopped even if the
browser is closed – WP-Cron leaves it alone until you press Resume.

Connection checks before backing up

Every selected destination is verified before the backup starts. If FTP is
missing its host, username or password, or Google Drive has not been connected,
the backup is refused straight away with a message naming the problem, rather
than building a large package and failing at upload time. All problems are
listed at once so they can be fixed in a single pass.

Choosing a destination

On the Backup Now screen you pick exactly one destination – the three
choices are radio buttons, so only one can ever be selected and one is always
chosen for you. If you pick a destination that is not set up yet, the backup
stops before it starts and tells you what is missing.

Scheduled backups work differently: under Settings you can tick several
destinations, and every scheduled run is mirrored to all of them.

Seamless restore

The restore screen follows the correct order so a moved site just works:

1. The package is fetched (from FTP or Drive if there is no local copy).
2. The database is imported.
3. URLs are replaced across every table, including serialised values, so the site
   functions at its new address.
4. Files are unpacked over the WordPress root.
5. Caches and rewrite rules are flushed.

You can restore the database, the files, or both, and choose a different site
address in the same step.

Features

• Scheduled backups (hourly to monthly) with a configurable start time.
• Retention by count and/or age – old backups are removed automatically.
• Optional AES-256 encryption for packages at rest.
• One-click site migration / domain change.
• Partial restores (database only, files only).
• Time-sliced processing, so large sites never hit a PHP timeout.
• Works on shared hosting: jobs continue via WP-Cron even if the browser closes.
• WP-CLI commands for scripted backups and restores.
• Detailed activity log per backup.

Connecting Google Drive

Google Drive needs your own OAuth client, because only then are the backups
yours alone. Creating one is a one-off, and takes a few minutes:

1. Open the Google Cloud Console, create a project, and enable the Google
   Drive API.
2. Under APIs & Services -> Credentials, create an OAuth client ID of
   type Web application.
3. Add the redirect URI shown on the plugin’s settings screen, with the
   Copy button next to it. The plugin warns you if the file you paste was
   created for a different site, which is the usual reason this step fails.
4. Download the JSON file Google offers, and paste the whole thing into the
   Credentials file box on the settings screen. The client ID and secret are
   read out of it for you, so there is nothing else to copy by hand.
5. Save, then press Connect Google Drive and choose your account.

If you would rather type the values yourself, use the Enter them by hand
instead link.

“Google no longer accepts this connection”

Google ends a connection for a few reasons, and the plugin names which one
applies:

• Access was revoked, either by you or from the Google account’s security
  settings.
• The consent screen is still in Testing. This is the one that catches
  people out: while an OAuth app is in Testing, Google expires these
  connections after 7 days, so a working setup stops working on day 8. Move
  the consent screen to In production in the Google Cloud Console, then press
  Connect Google Drive again.
• The OAuth client was deleted in the Google Cloud Console. Create a new
  one, paste its file, and connect again.

Temporary problems – the site being offline, Google being briefly unavailable –
are never treated as a dead connection, so a network blip will not cost you a
working setup.

Replacing your credentials also disconnects the account, because a stored
connection only ever works with the client that issued it. The plugin does this
for you and tells you to reconnect, rather than leaving a connection that looks
fine and then fails during an overnight backup.

Third-party services and privacy

RSN Site Backup Pro does not send backups, analytics, or other site data to RSN.
It only contacts external services that an administrator explicitly configures:

• Google Drive (optional): after an administrator connects a Google account,
  the plugin sends backup archives to that account through the Google Drive API.
  A backup can contain the site’s database, files, and therefore personal data
  held by the site. Google Drive use is governed by Google’s Terms of Service
  and Google’s Privacy Policy.
• FTP / FTPS (optional): after an administrator configures a server, the
  plugin sends backup archives and uses the connection credentials only to
  communicate with that administrator-selected server. The server operator’s
  own terms and privacy policy apply.

The plugin stores the destination settings and Google OAuth credentials in this
WordPress installation. Site owners should update their site’s privacy policy
to explain their chosen backup destination and the data contained in backups.