Protecting Your Site
There are two layers of protection: undo data for every fix (both versions) and full backups of the database, themes and plugins (Premium).
Undo Data for Fixes (Both Versions)
Every fix records what it changes before it runs. Database cleanups (revisions, spam, trash, transients, orphaned metadata and others) save the deleted rows, so they can be restored for 30 days. If a cleanup reaches the limit for how much backup data may be stored, it stops and leaves the remaining rows untouched; run it again to continue. Everything is undone under Fixes → Applied & history, and undo never requires an active licence.
Backups (Premium)
Under Tools → Backups you choose what to back up:
- Database - every table of the WordPress database, as a compressed SQL file
- Themes - all installed themes, as a ZIP file
- Plugins - all installed plugins, as a ZIP file
- Database, themes and plugins - all three in one ZIP file
Uploads (the media library) and wp-config.php are not included. Keep a host or off-site backup for those. Large sites are processed in chunks to avoid timeouts.
Storage
Backups are stored in wp-content/tsa-backups/:
- File names end in 32 random characters
- The folder is protected with .htaccess and web.config; on nginx the Backups screen shows the rule to add to the server configuration
- Downloads are only offered to administrators, through WordPress
- Backups older than 30 days are deleted automatically
Backups are kept on the same server as the site - keep a copy elsewhere too.
Restoring
Before a restore starts, a restore point of the same type is created so you can go back. Damaged or truncated backups and archives with unsafe file names are refused before anything changes, and only the kind of statements a backup made by the plugin contains are run. A database restore swaps in every table in one step at the end. Keep the page open until the restore has finished.
On multisite, only a network super admin can use backups and restores.