PBS with WORM/Immutable Storage for Backup Chunks

[pingtrace]

Hi everyone,

Can PBS work with WORM/immutable storage for the backup chunks?

For example, if existing chunks are stored in an immutable/WORM folder, can PBS continue to perform regular backups by simply creating new chunk files and creating new index files that reference existing unchanged chunks?

If existing chunks cannot be modified or deleted, can PBS still reuse/reference those chunks for subsequent backups?

Can the metadata/index files be stored in a separate normal writable folder (where files can be created, modified, and deleted), while the actual chunk files are stored on immutable storage?

How does PBS Garbage Collection handle an immutable datastore? If GC cannot modify or delete a chunk, does it:

• fail with an error and stop,
• log a warning and skip the chunk, or
• handle it in another way?

The idea is that each individual chunk would have its own immutable retention period. After the defined retention period expires, the chunk would become writable/deletable again.

Thanks!

 

[Chris]

Hi, this is currently not possible, see https://bugzilla.proxmox.com/show_bug.cgi?id=4293 Since I'm currently working on a immutable sync with retention periods, so might take a closer look at this as well, but no promises or ETAs

 

[Supaman]

Not immutable, but you can:
- protect each backup
- do not run gc / prune

Furthermore: you can create a user account fpr pve usage, which has the rights "backup". this user can only write (delvier), protect and restore backups, but not delete.

 

[Frank-75]

But can protection be enabled for a specific amount of time?