Nextcloud Backup creates multiple files

[FullyBorked]

I haven't updated just yet.  I do rely on these backups and I'm confused a bit reading all this.  Can someone clarify what's going on here?  So, each backup file isn't a full backup?  For example with a restore we'd need a full and a diff?  I clean up backup files on the Nextcloud side, want to make sure I understand this so I don't blow out a full backup and bork up my ability to restore if needed. 

Or am I misunderstanding and this just creates a full backup on ANY change?  Along with just a goofy naming convention. 

[franco]

Instead of backing up a file per invoke it backs up your actual backup content on the system all at once.

From a pure technical perspective you still have all your backups.  From a UX perspective both the old and the new way have upsides and downsides.


Cheers,
Franco

[Patrick M. Hausen]

Instead of backing up a file per invoke it backs up your actual backup content on the system all at once.

And which of the multiple files do I pick for a restore?

[franco]

The one with the appropriate timestamp? I don't quite understand the fuzz except for readability and host name missing. It mirrors the backup functionality of how System: Configuration: History has always worked.


Cheers,
Franco

[Patrick M. Hausen]

It mirrors the backup functionality of how System: Configuration: History has always worked.

So all the files are a complete backup each. I must admit I never looked closer into the mentioned part of the menu. Only configuration backup and restore. And os-nextcloud-backup nicely mirrored what you would get with a manual download plus renaming/archiving per day.

So please don't get this wrong: my only complaint is about readability and the missing hostname.

But I will revisit the git based mechanism, anyway, because that includes a log of who did the change in a situation with more than one admin.