Experimental: Backups are still new...

Thorsten Luckmann · 2026-07-27T07:20:08+00:00

Hi Pascal, ein Vollbackup wiederherzustellen dürfte ja nur gehen, wenn HTProtect auf der Webseite lauffähig ist, bzw. die Seite überhaupt noch lauffähig ist. Ebenso ein Download über die HTProtect-App. Alternativ über FTP geht natürlich, insofern das Backup im Falle eines "Gaus" noch existiert. Ist da noch etwas in der Planung? Eventuell eine Möglichkeit, ein Backup automatisiert extern zu speichern? Alles aus eine Hand, statt mit weiteren Programmen zu arbeiten, wäre genial. Daher die Frage. ;-)

Thorsten Luckmann

Hi Pascal, restoring a full backup probably only works if HTProtect is running on the site, or if the site is even still up. Same goes for downloading via the HTProtect app. Alternatively, you can use FTP, assuming the backup still exists in case of a disaster. Is there anything planned for this? Maybe a way to automatically save backups externally? Having everything handled in one place instead of juggling multiple programs would be awesome. Hence the question. ;-)

Pascal

Hi Thorsten, expanding the backup feature is definitely on the roadmap with the exact goal of "everything from one source." Sending backups to external sFTP storage (like Hetzner Storage Box, etc.) is also planned. But that’s not a priority right now. Offsite backups will come only after onsite proves to be solid.

Recently, I created a consolidated backup directory at
/administrator/_htprotect_backups/
where rollback points, core reference ZIPs, and full/DB backups go (basically everything that takes up more storage space).

Thorsten Luckmann

Thanks for the info. That sounds super interesting. I also noticed that when restoring a full backup, new content isn’t deleted. I once renamed a file via FTP as a test, but it was still there after the restore. Is that how it’s supposed to work?

Pascal

Yes, that's how it's supposed to be, and that's also how Akeeba Backup (Pro) behaves when restoring from the backend or via Kickstart into an existing directory without emptying it first.

Further development of the backup and restore features beyond the "basic functionality" will follow once higher priority tasks are completed.

deevau

It would be great if, during the restore, you could choose whether to completely clear the database and webspace (except for htprotect, of course) so you can have a clean site right away.

Pascal

deevau

Is it now possible with 2.7.4+:

Igor

Hello. Have you considered using Git for the website files, as a storage for code files, etc.?

Pascal

Hi Igor,

Good point – but in my opinion, Git isn’t the right tool for backups:

Git is made for code/text and quickly gets huge and slow with images, media, and large files.
It also doesn’t properly back up the database – which is the most important part of a Joomla/WordPress site.
A commit history isn’t a full, restorable backup you can rely on in an emergency.

That’s why we use full backups (files + database) as snapshots. We’re planning to add the option to store these externally via SFTP.

For just versioning your own templates/customizations, Git is obviously great – but that’s a developer workflow, not a site backup.

Cheers
Pascal