23
[AIP] Portabase (v1.34) now supports file and directory backups (github.com)
submitted 2 weeks ago by to c/selfhosted@lemmy.world
3 comments fedilink hide all child comments
 

Hi everyone,

It's been a while since I last posted here! I'm happy to announce that we've released Portabase 1.34!

Repository: https://github.com/Portabase/portabase (on the road to 2k stars)

For those unfamiliar with Portabase, it's an open-source, self-hostable backup and restore platform designed for data retention, disaster recovery, and homogeneous migrations.

Until now, Portabase supported 10 data sources (including PostgreSQL, MySQL, MariaDB, MongoDB and Docker volumes).

With v1.34, we're introducing our 11th data source: files and directories!

There are 3 ways to back up your files:

  • Archive (logical backup): creates a full .tar.gz of the selected directory.
  • Snapshot (incremental): uses Restic under the hood to provide incremental backups with deduplication, reducing storage usage.
  • Sync: synchronize files and directories to a destination. This is a direct copy, not a restorable backup.

What's new in 1.34?

  • Support for file and directory backup/restore (obviously)
  • UX improvements and UI fixes
  • Multiple security fixes, thanks to users who reported vulnerabilities
  • DACPAC support for Microsoft SQL Server (in addition to BACPAC, and native BACKUP DATABASE support is also on the way)
  • Helm chart improvements

Important: If you're upgrading and want to use the new file and directory backup features, make sure to update your agents as well.

As always, if you encounter a bug, please open an issue on GitHub. And if you like the project, consider giving us a star! It means a lot to us and helps the project gain visibility.

Thanks to everyone using, testing, contributing to, and supporting Portabase!

all 3 comments

sorted by: hot top controversial new old
[–] [S] 15 points 2 weeks ago*

AI Disclaimer:

AI is used for debugging, implementing simple features and documentation. Every line of code (written by hand or generated by AI), is manually reviewed before being merged.

  • Review: Hint (with CodeRabbit)
  • Implementation: Assisted
  • Documentation: Pair
  • permalink
  • fedilink
  • source
    •
    [–] 3 points 1 week ago (1 child)

    I keep my Docker app data on ZFS, with sanoid snapshots every 15 minutes and syncoid replicating hourly between two boxes, so plain file backup is mostly covered by the filesystem for me. Where a tool like this would still earn a spot is the database side, since a snapshot of a running Postgres isn't the same thing as a proper dump. Does the Restic snapshot mode let you restore a single directory to a different path, so you can test a restore without touching the live copy?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • 4 comments in c/opensource@programming.dev view that post
    [–] 2 points 3 months ago (3 children)

    Nice timing I'm running SQLite + Redis on Railway and was just thinking about backup strategy. Does Portabase handle Railway volumes or only self-hosted Docker environments?

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 1 point 3 months ago (2 children)

    For databases, you only need to provide the URL, port, and credentials. Portabase then connects using the database’s standard protocol, making it hosting-agnostic (so you can backup databases hosted in self-managed Docker environments, Kubernetes clusters, or cloud platforms).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • 2 comments in c/opensource@lemmy.ml view that post
    [–] 1 point 3 months ago (1 child)

    encrypted differential backups like in restic when?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •