Feature: JPA format import (Akeeba migration) #20

New Issue

2026-06-02T20:29:33Z

jmiller commented

2026-06-02 20:29:33 +00:00

Support importing existing Akeeba Backup JPA archives for migration.

Description

Sites migrating from Akeeba Backup Pro have existing backups in JPA format. Adding a JPA unarchiver allows restoring those archives without Akeeba installed.

Requirements

JPA archive format parser
Extract JPA to same staging format as ZIP
RestoreEngine supports JPA input
Read-only (no need to create JPA, only extract)

Implementation Notes

JPA format spec can be reverse-engineered from Akeeba Kickstart source (Unarchiver/JPA.php). Binary format with file headers containing path, size, permissions, and compressed data.

Support importing existing Akeeba Backup JPA archives for migration. ## Description Sites migrating from Akeeba Backup Pro have existing backups in JPA format. Adding a JPA unarchiver allows restoring those archives without Akeeba installed. ## Requirements - [ ] JPA archive format parser - [ ] Extract JPA to same staging format as ZIP - [ ] RestoreEngine supports JPA input - [ ] Read-only (no need to create JPA, only extract) ## Implementation Notes JPA format spec can be reverse-engineered from Akeeba Kickstart source (Unarchiver/JPA.php). Binary format with file headers containing path, size, permissions, and compressed data.

jmiller added the type: feature priority: low component: engine status: blocked labels 2026-06-02 20:29:33 +00:00

jmiller commented

2026-06-02 20:29:33 +00:00

Testing Plan

TC-F7.1: JPA extraction

Take an existing Akeeba JPA backup file
Import via MokoJoomBackup restore
Verify all files extracted correctly
Verify database.sql (if present) is importable

TC-F7.2: Large JPA

Import a JPA > 500 MB
Verify extraction completes without timeout

TC-F7.3: Corrupt JPA

Truncate a JPA file
Attempt import
Verify clear error message

## Testing Plan **TC-F7.1: JPA extraction** 1. Take an existing Akeeba JPA backup file 2. Import via MokoJoomBackup restore 3. Verify all files extracted correctly 4. Verify database.sql (if present) is importable **TC-F7.2: Large JPA** 1. Import a JPA > 500 MB 2. Verify extraction completes without timeout **TC-F7.3: Corrupt JPA** 1. Truncate a JPA file 2. Attempt import 3. Verify clear error message

jmiller referenced this issue from a commit

2026-06-02 23:56:24 +00:00

feat: dashboard widget (#18), differential backups (#19), JPA import (#20)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#20