Hi Christian, When I think about it, I think snapshot as a “bit-perfect copy” of a filesystem. Backup is just a fancy name for copying files with as much metadata as possible around them (permissions, ownership data, timestamps and whatnot). On the other hand, the repository which we keep this “versioned copies” is a backup. It just contains multiple backups inside. Maybe we can go “full Borg”, and call backup destinations as “repositories" and snapshots as “backups”, I don’t know, but changing the terminology will need adjustment to many of the jargon BIT is built upon. On the other hand, Borg calls itself as an “archiver”, but it’s an understatement and underselling of both BIT an Borg. :) Hope this helps, Cheers, Hakan
On 5 Nov 2024, at 12:02, c.buhtz@posteo.jp wrote:
Hello folks,
I am interested in your opinions about this.
Looking into my foggy memory it seems that I somehow asked this question before. But I couldn't find out when and where. So my apologize if this is a duplicate.
In my experience around BIT I would say that the term "Backup" is more appropriate for what we currently call "Snapshot". So I would like to change that.
- For someone not knowing BIT (e.g. potential new users and translators) the term "Backup" is clearer. - Snapshot might be understood by some people as an image of the file system. - When writing about BIT (in Issues, Forums, etc) most of the time I do use the term "backup" out of the stomach without thinking about it.
I do understand that "Snapshot" is kind of fancy and points to the timeline feature. But I would prefer to use the technical correct term "Backup" instead of a marketing term.
What do you think?
Regards, Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org