The recovery lifecycle
FortisRestore captures site files, database, and configuration in an AES-256 encrypted .fts recovery point. A dependable recovery plan has four parts.
Build and encrypt a complete recovery point.
Keep a copy outside the website hosting account.
Confirm the archive manifest and payload are intact.
Restore to staging and test the recovered site.
FortisRestore for Joomla
Administration begins at Components → FortisRestore.
Requirements
- Joomla 4, 5, or 6
- PHP 8.1+; PHP 8.3 recommended
- ZIP with AES-256 support
- OpenSSL, JSON, database, and cURL
- Writable secure backup and work locations
- Free disk space larger than the estimated archive
The installer preflight blocks unsupported environments. After installation, run the Configuration Check and resolve every red item before relying on backups.
Installation and first backup
- 1
In Joomla Administrator, open System → Install → Extensions and upload the FortisRestore component ZIP.
- 2
Open Components → FortisRestore and run the server and site configuration check.
- 3
Save the recovery key somewhere secure outside the Joomla site and hosting account.
- 4
Open License, paste the key from your FortisRestore account, and select Verify.
- 5
Return to Dashboard and select Create Backup. Wait for Encrypted backup verified.
- 6
Download the first archive, then prove it with a staging restore.
Backups and archive management
A persistent job exports database tables in batches, adds Joomla files, encrypts the archive, and verifies it. Changing FortisRestore tabs does not stop the job; returning to Dashboard or Backups resumes visible progress.
- Download: save a local recovery point to your computer.
- Delete: remove the selected local recovery point after confirmation.
- Fetch: retrieve a remote-only archive; Download and Delete return afterward.
- Upload archive: import an older
.fts. Supply its original recovery key when it came from another site.
Staging restore and production replacement
- 1
Choose a verified local archive or fetch a remote-only one.
- 2
Inspect its site identity, date, size, Joomla version, and integrity status.
- 3
Create a staging restore in a separate folder and database prefix.
- 4
Open frontend and administrator; verify the template, extensions, forms, email, and critical workflows.
- 5
Run the staging health check. A green checked staging entry means the copy passed—it is not the live site.
- 6
Use production replacement only after staging proof and during a maintenance window. Preserve the rollback created by Fortis until validation finishes.
Schedules, retention, and email
Under Schedules, enable automatic protection, choose the frequency, and set retention. Ensure Joomla Scheduled Tasks or a server cron runs reliably. Retention removes old eligible backups only after newer recovery points succeed.
Under Settings → Email notifications, select the recipient and success/failure events. Joomla Global Configuration must send a successful test email first.
Joomla migration
Select a verified archive under Migrations, enter the destination SFTP connection, destination web path, and URL, then start the persistent transfer. Open the supplied recovery URL on the destination, enter its database settings, review the summary, and confirm. Remove temporary SSH access after completion.
Joomla license and updates
Copy the key from fortisrestore.app → Account. Paste and verify it under FortisRestore → License. Fortis synchronizes the protected Joomla download key. Before an update, confirm a verified backup, read release notes, and test major changes on staging.
FortisRestore for WordPress
Administration begins at WordPress Admin → FortisRestore.
Requirements
- WordPress 6.0 or later
- PHP 8.1+; PHP 8.3 recommended
- ZIP with AES-256 support
- OpenSSL and cURL
- Writable protected storage
- At least 256 MB free space beyond the estimate
Open Settings → System readiness to verify PHP, extensions, storage permissions, and disk space.
Installation and first backup
- 1
Open Plugins → Add Plugin → Upload Plugin, select the FortisRestore WordPress ZIP, and activate it.
- 2
Open FortisRestore → Settings and confirm each readiness row says Ready.
- 3
Open License, paste your FortisRestore key, and select Activate.
- 4
Create a backup from Dashboard and wait for the Fortis Backup Complete shield.
- 5
Download the archive before enabling remote-only storage.
- 6
Prepare an empty staging folder and separate database, then prove the first restore.
Persistent WordPress backups
Fortis exports WordPress tables, captures files and wp-config.php, encrypts every archive entry, and verifies the result. Progress is stored on the server, so changing tabs does not stop the backup. Backups lists local and remote-only recovery points; use Fetch to return a remote archive before download or restore.
WordPress staging restore
A restore requires an empty destination folder and an existing empty database that the current database user can access. Create both in your hosting panel.
- 1
Fetch the recovery point if it is remote-only.
- 2
Enter the full empty destination path and empty database name.
- 3
Start Restore. Fortis copies files, imports tables, and rewrites WordPress home and site URL.
- 4
Verify frontend, /wp-admin, permalinks, forms, ecommerce, themes, plugins, cron, and email.
- 5
Replace production only after a successful staging test and during a controlled maintenance window.
WordPress schedules and notifications
Under Schedules, enable Daily or Weekly backups and choose local retention. WordPress Cron launches the persistent job. Low-traffic sites should invoke wp-cron.php from a real server cron. Configure alerts under Settings; authenticated SMTP is recommended.
WordPress migration
Under Migrations, select an archive and enter the host, port, user, private-key path, destination path, and URL. The SFTP path is relative to the account home—for example public_html/new-site. Fortis writes to fortis-incoming and resumes a partial transfer. Install FortisRestore on the destination and complete a guided restore there.
WordPress license and updates
Paid licenses enable remote storage, schedules, migrations, and protected updates. WordPress shows new releases in its normal Plugins interface; the package is delivered only to an eligible active license.
Remote storage
Choose the provider, enter the destination you want, save, and test the connection. With remote-only storage enabled, Fortis verifies the upload before removing the local archive.
| Provider | Configuration and behavior |
|---|---|
| Dropbox | Connect an account or enter a token. You choose the destination. App Folder permissions store data under Dropbox Apps; root-level folders require Full Dropbox access. |
| Google Drive | Connect the Google account that owns the destination. Fortis can upload and fetch recovery points. |
| Amazon S3 | Enter the endpoint, region, bucket, prefix, access key, and secret key. |
| Backblaze B2 | Use the B2 S3-compatible endpoint, region, bucket, and application key. |
| WebDAV | Enter an HTTPS WebDAV URL, username, password, and folder. |
| SFTP | Use key authentication. Store the private key outside the public website. |
| Mounted storage | Enter a writable server path outside the website, such as a second disk or protected account folder. |
The .fts recovery point
An .fts contains a manifest, database export, site files, and configuration encrypted with AES-256. Renaming the extension does not decrypt or convert it.
- Keep at least one copy outside the website hosting account.
- Use a different provider or physical failure domain for critical sites.
- Never edit an archive after creation.
- Periodically fetch a remote archive and perform a staging restore.
- Treat recovery keys, access tokens, and private keys as secrets.
Troubleshooting
Backup job not found
Return to Dashboard and start a new backup. If it repeats, confirm the protected work directory is writable, check disk space, and inspect PHP error logs.
The progress bar disappears
Update FortisRestore. Current releases persist job state on the server and resume the display when you return.
I cannot find the remote upload
Confirm the connected account, provider permission scope, and exact user-selected destination. Dropbox App Folder access appears under Apps.
Notification email never arrives
Test CMS mail first, confirm the recipient, inspect spam, and verify SPF/DKIM. Joomla uses Global Configuration; WordPress commonly needs SMTP.
The restored site opens the source URL
Update FortisRestore and rerun the restore. Current builds rewrite destination configuration and WordPress home/site URL.
SFTP cannot find the destination
Use the path visible after SFTP login, usually relative to the account home, such as public_html/new-site.
Update download returns 403
Verify the license again and confirm the subscription is active and within its site limit.
Emergency recovery checklist
- 1
Stop changes and place the damaged site in maintenance mode.
- 2
Preserve logs and, if practical, take a final snapshot before replacement.
- 3
Choose the newest known-good archive, not merely the newest file.
- 4
Fetch remote media and verify archive integrity.
- 5
Restore to staging and test administrator access plus critical workflows.
- 6
Replace or migrate during a maintenance window.
- 7
Clear caches and validate email, forms, payments, scheduled tasks, DNS, SSL, and logs.
Need help?
Send your CMS/version, FortisRestore version, PHP version, exact error, and operation time. Never send passwords, tokens, private keys, or recovery keys.