Products

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

Dashboard Overview

The Dashboard is the default landing page when you open MokoSuiteBackup in the Joomla administrator. It gives you a real-time overview of your backup status, system health, and quick access to common actions.

Status Cards

Four clickable cards appear at the top of the dashboard:

Quick Actions

The Quick Actions panel provides:

• Backup Now — Select a profile from the dropdown and click to start an immediate backup. The full-screen backup screen shows a real-time progress bar, and on completion offers a View backup record button.
• Navigation links — Direct access to Backup Records, Backup Profiles, Content Snapshots, Scheduled Tasks, and Update Sites.

System Health

The System Health panel runs automated checks and displays pass/fail status for:

• PHP Version — Must be 8.3 or higher (required for Joomla 6.x)
• ZipArchive — Required PHP extension for ZIP archives
• AES-256 Encryption — Requires libzip 1.2.0+ for encrypted archives
• Backup Directory — Checks the configured directory exists and is writable
• Free Disk Space — Warns if less than 1 GB free

Default Directory Warning

If any published profile stores backups in the default directory inside the web root (administrator/components/com_mokosuitebackup/backups), a warning banner is displayed. For better security, configure a backup directory outside the web root.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

Positioning

MokoSuiteBackup is a native Joomla 6 full-site backup and restore solution (Joomla 4/5 supported) built to replace Akeeba Backup Pro. Like Akeeba it dumps the database, archives the files, and can preserve or restore configuration.php, and it integrates with the same Joomla subsystems — the console, the Scheduler, and the extension update flow. For the common "back up my site, restore it, do it automatically, and back up before I update" workflow it aims for parity.

Feature Parity at a Glance

How to Move from Akeeba

MokoSuiteBackup does not read Akeeba's .jpa/.jps archives or import Akeeba profiles — it uses its own profiles and archive formats, so migration is a parallel cut-over rather than an import:

1. Install the pkg_mokosuitebackup package (plugins auto-enable).
2. Set live_site in Global Configuration to your full site URL including the scheme, so CLI/cron archive names resolve the correct host.
3. Recreate your profiles — pick the archive format, set an encryption password if wanted, and configure remote destinations.
4. Recreate your schedule with a Scheduled Task, the web-cron URL, or a CLI cron entry running mokosuitebackup:run.
5. Re-point backup-on-update — turn off Akeeba's, enable MokoSuiteBackup's Backup before update / Backup before uninstall.
6. Run a test backup and restore, then uninstall Akeeba (ideally with Backup before uninstall enabled).

Backup-on-Update — the Akeeba-Style Flow

When you click Install the update, you're redirected to a dedicated full-screen backup screen with a real progress bar. An opt-in auto-continue checkbox (ticked by default) hands you straight back to the update the moment the backup completes — no second manual click; untick it to stop on completion and get a link to the new backup record plus a manual Continue the update button. No backup runs synchronously inside the update request (which is what used to white-screen large sites). While it runs, a “do not close or switch windows” warning and a full-screen “update is running” overlay stay on screen, and a double-confirmed Cancel is available. If the backup fails, the update is blocked outright — your only choices are to retry the backup or go back without updating. The same screen fronts extension updates and uninstalls.

What MokoSuiteBackup Adds

• Content snapshots — capture just articles, categories and modules for a fast content-only rollback.
• Snapshot transfer / master→slave injection — export a snapshot as a portable .msbsnap file, import it on another site, or push it directly into another site's Web Services API.
• Web Services API — manage backups and inject snapshots remotely.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

AES-256 Encryption

Encryption is per-profile and driven entirely by the profile's Encryption Password in Archive Settings — a blank value means no encryption, any non-empty value turns AES-256 on. Support depends on the archive format:

• ZIP — WinZip-compatible AES-256 applied per entry after the archive is written (requires PHP 7.2+ with libzip 1.2.0+). File contents are encrypted; filenames stay visible.
• 7z — native 7z CLI encryption with header encryption (-mhe=on), so filenames are hidden too (requires p7zip / 7-Zip on the server).
• tar.gz — encryption is not supported; the backup completes unencrypted and logs a warning.

If encryption is configured but the encryption step fails, the plaintext archive is deleted and the backup is recorded as failed, so an unencrypted copy is never left behind.

Data Sanitization

Independently of encryption, a profile can scrub the database dump before it is archived: sanitize passwords (with preserve super admin), sanitize emails, and sanitize sessions. Credentials in configuration.php are also stripped automatically. Use encryption and sanitization together when shipping backups off-site.

SHA-256 Integrity

A checksum is computed after archive creation. Use the Verify Integrity button to detect corruption or tampering.

MokoRestore Restore Script

Self-contained restore.php with CSRF protection, pre-flight checks, and encrypted-archive support. Upload it to any PHP server for a bare-server restore. See Restore & MokoRestore.

Backup Directory

Protected with .htaccess (Deny from all) and index.html. For best security, set a backup directory outside the web root.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

REST API Endpoints

Routes are registered by plg_webservices_mokosuitebackup and are wire-compatible with the mcp_mokosuitebackup MCP server. The API Application and the Web Services plugin must be enabled. All routes require authentication — send a Joomla API token in the X-Joomla-Token header (or a Bearer token):

X-Joomla-Token: <your-api-token>
Accept: application/json

Base URL: /api/index.php/v1/mokosuitebackup/.... Each action also enforces a component ACL permission; a failed check returns HTTP 403.

Backup Endpoints

Snapshot Endpoints

Content snapshots capture selected content types (articles, categories, modules) as portable JSON. All require the mokosuitebackup.snapshot.manage permission.

MCP Server

The mcp_mokosuitebackup MCP server is wire-compatible with these endpoints, so an AI assistant can start backups, list records, manage profiles, and create or inject content snapshots remotely.

CLI

php cli/joomla.php mokosuitebackup:run --profile=1
php cli/joomla.php mokosuitebackup:run --profile=2 --description="Pre-deploy"

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

Storage Backends

A profile can push each finished archive to one or more remote destinations, managed per profile in the profile's Remote Destinations panel. Each destination is stored as one row (with its settings as JSON) in #__mokosuitebackup_remotes.

SFTP, S3 and Google Drive appear in the Add/Edit modal's Type selector; FTP is a fully supported backend used by existing/imported destinations. All uploaders are pure PHP with cURL — no SDK dependencies.

S3-Compatible Services

• AWS S3: https://s3.amazonaws.com
• Wasabi: https://s3.wasabisys.com
• Backblaze B2: https://s3.us-west-001.backblazeb2.com
• MinIO: your server URL

Keep Local Copy

Each destination has a Keep local copy toggle (default on). When off, the local archive is removed once it has uploaded to every enabled remote without any upload failure.

Remote Retention Pruning

RetentionManager is the single retention authority and prunes remote copies as well as the local one. When a record is pruned by age or count it deletes the DB row, unlinks the local archive and its log, and deletes the archive from every currently enabled remote destination for that profile. Remote deletion is idempotent and best-effort — a failure is logged but never blocks local pruning. The shared standalone restore.php is intentionally never pruned from remotes.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

Backup Types

Set on the profile's General tab (default full):

Default Profile

The component-wide default profile (Options > General, defaults to profile 1) is what runs when a trigger doesn't name a specific profile — including the pre-update / pre-uninstall full-screen backup, the dashboard Backup Now screen, and a web-cron call with no profile_id.

Profile Tabs

• General: title, description, backup type
• Archive: format (zip, tar.gz, 7z), compression level, split size, backup directory, archive name format, Include MokoRestore (None / Wrapped / Standalone), encryption password
• Sanitization: scrub the DB dump — sanitize passwords (with preserve super admin), sanitize emails, sanitize sessions
• Filters: exclude directories, files (glob wildcards, e.g. *.bak), and database tables
• Retention: per-profile overrides of the global cleanup age/count (a value of 0 falls back to the global default)
• Notifications: email recipients, notify user groups, notify on success/failure, plus ntfy topic/server/token

Remote Destinations

Off-site upload is configured per profile with remote destinations (SFTP, FTP, S3, Google Drive). The Keep local copy setting lives in each destination's Add/Edit modal and controls whether the local archive is removed after a fully successful upload to every enabled remote. See Remote Storage.

Differential Backups

Compares the current filesystem against a manifest from the last full backup; only new/modified files are included, while the database is always fully dumped. Falls back to a full backup if no base manifest exists.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

Installation

1. Download the latest pkg_mokosuitebackup-*.zip package from Releases
2. Go to System > Install > Extensions in the Joomla Administrator
3. Upload the package ZIP (or use Install from Folder / Install from URL)
4. The single package installs the component, all plugins, the admin module and the CLI/Web Services resources in one step, and auto-enables its plugins
5. Wait for the postflight to complete — the installer verifies that every bundled child extension actually registered and that the component's schema tables exist, and reports an error rather than a false "installed successfully" message if anything is missing

Package Contents

Requirements

• Joomla 6.x or later (Joomla 4/5 supported; Scheduled Tasks need 4.1+)
• PHP 8.3+ required (Joomla 6)
• MySQL 8.0 or MariaDB
• PHP extensions: ext-zip, ext-curl, ext-ftp, ext-mbstring, ext-pdo_mysql

First Backup

1. Navigate to Components > MokoSuiteBackup (the admin Backup menu, with Dashboard, Backup Records, Content Snapshots and Backup Profiles)
2. A default backup profile is pre-configured
3. Open Dashboard, select the profile from the dropdown and click Backup Now
4. A full-screen backup screen runs the stepped backup with a real-time progress bar; on completion a View backup record button links to the new record

Post-Install Options

Several capabilities are Super User only and off by default. Open Components > Backup > Options to enable Backup before update / Backup before uninstall, Allow Snapshot Injection (on a receiving/slave site), confirm the Default profile and backup directory, and set email/ntfy notifications.

Documentation

Full documentation is on the MokoSuiteBackup Wiki.

Details

Last Updated: July 14, 2026

• Applicable Software: MokoWaaS (Joomla)
• Applicable Version: 02.64.00

What is MokoSuiteBackup?

MokoSuiteBackup is a comprehensive backup and restore solution for Joomla 6 (Joomla 4/5 supported), built as a complete replacement for Akeeba Backup Pro. It provides full-site backups (database + files), multiple backup profiles, scheduled tasks, remote storage (FTP, Google Drive, S3), AES-256 encryption, content snapshots, automatic backup-before-update protection, and a standalone restore script.

Key Features

• Full, database-only, files-only, and differential backup types
• Multiple backup profiles with independent settings
• Backup before update & uninstall — a full-screen backup fronts Joomla core updates and any extension update or uninstall, so you always have a fresh restore point without white-screening large sites. An opt-in auto-continue checkbox (on by default) hands back to the update the moment the backup finishes; a prominent “do not close or switch windows” warning and a full-screen “update is running” overlay guard the process; and you can Cancel at any time (double-confirmed). If the pre-update backup fails, the update is blocked — you retry the backup or go back without updating
• Content snapshots & transfer — capture articles, categories and modules and move them between sites as a portable .msbsnap file, or push them master→slave directly via the injection API
• Joomla Scheduled Tasks integration plus web-cron for automated backups
• Remote storage: FTP/FTPS, Google Drive, Amazon S3 (+ Wasabi, B2, MinIO), with retention that prunes remote copies too
• AES-256 archive encryption for GDPR compliance
• MokoRestore standalone restore script for bare-server restores
• SHA-256 integrity verification
• Email and ntfy notifications on success, warning and failure
• REST API compatible with the MokoSuiteBackup MCP server
• AJAX step-based engine for shared hosting
• One-click Akeeba Backup Pro migration and JPA archive import
• Admin dashboard status widget

Documentation

Full documentation is available on the MokoSuiteBackup Wiki.