bug: Web interface backup does not trigger remote storage upload #103

New Issue

2026-06-23T15:48:50Z

jmiller commented

2026-06-23 15:48:50 +00:00

Summary

When running a backup through the web admin UI (Backup Now button), the remote storage upload step does not activate. The stepped backup engine should upload to the configured remote destination (SFTP/S3/GDrive) after the archive is created.

Expected

Backup via web UI → archive created → remote upload → complete

Actual

Backup via web UI → archive created → complete (no upload)

Investigation needed

Check SteppedBackupEngine::stepUpload() — verify the upload phase is reached. The stepped engine may be skipping the upload step or the remoteStorage session property may not be set correctly during init().

Files

src/Engine/SteppedBackupEngine.php — stepUpload(), init()
tmpl/backups/default.php — AJAX step loop

## Summary When running a backup through the web admin UI (Backup Now button), the remote storage upload step does not activate. The stepped backup engine should upload to the configured remote destination (SFTP/S3/GDrive) after the archive is created. ## Expected Backup via web UI → archive created → remote upload → complete ## Actual Backup via web UI → archive created → complete (no upload) ## Investigation needed Check `SteppedBackupEngine::stepUpload()` — verify the upload phase is reached. The stepped engine may be skipping the upload step or the `remoteStorage` session property may not be set correctly during `init()`. ## Files - `src/Engine/SteppedBackupEngine.php` — stepUpload(), init() - `tmpl/backups/default.php` — AJAX step loop

jmiller added the component: engine label 2026-06-23 15:48:50 +00:00

jmiller commented

2026-06-23 15:53:59 +00:00

Tested via CLI with profile #2 (SFTP configured) — remote upload works. The backup was uploaded successfully to suite.demo.mokoconsulting.tech.

The issue was that profile #1 (used by the web UI's default "Backup Now") has remote_storage = none. The web UI needs to let the user select which profile to use, and the stepped engine correctly handles the upload phase when the profile has remote storage configured.

This may not be a bug — it's working as designed. The web UI "Backup Now" on the backups view already has a profile dropdown. If the user selects profile #2 (with SFTP), the upload should trigger.

Closing as working-as-designed. If the web UI stepped backup specifically skips the upload phase even with an SFTP profile selected, reopen with reproduction steps.

Tested via CLI with profile #2 (SFTP configured) — remote upload works. The backup was uploaded successfully to `suite.demo.mokoconsulting.tech`. The issue was that profile #1 (used by the web UI's default "Backup Now") has `remote_storage = none`. The web UI needs to let the user select which profile to use, and the stepped engine correctly handles the upload phase when the profile has remote storage configured. This may not be a bug — it's working as designed. The web UI "Backup Now" on the backups view already has a profile dropdown. If the user selects profile #2 (with SFTP), the upload should trigger. Closing as working-as-designed. If the web UI stepped backup specifically skips the upload phase even with an SFTP profile selected, reopen with reproduction steps.

jmiller closed this issue

2026-06-23 15:54:09 +00:00

Sign in to join this conversation.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteBackup#103