![]() ![]() Smallest distingt objects are file chunks of specified size. Please, correct me, if I have something wrong, as this or that might be still hypothetic:ĭuplicati is a backup and version tracking tool on file system level. I deliberately use “version” and “backup” only distict, not generalised, and I get along without “dblocks”, “dlists”, “database” and the cleanup procedure, which are beyond the basics. Let me reflect with my own words, trying to meet a detail level which covers many newbie comprehension questions in the forum, including mine. Thank you, with your help I feel to have a clearer view of Duplicati now. It throws away the bricks that are not needed anymore, then it puts the required bricks into new bags and puts them back into the box. The backup process explained tries to describe above wasted space removal with less technical terms:įrom time to time, Duplicati will notice that there are a few bags that contain bricks it does not need anymore. The smaller volume without obsolete contents is uploaded and the original volume is deleted, freeing up storage capacity at the backend. When a predefined percentage of a volume is used by obsolete backups, the volume is downloaded, old blocks are removed and blocks that are still in use are recompressed and re-encrypted. The backup protects against source deletions. One additional note on that is that they’re not deleted instantly, but periodically when enough build up, however this is just how wasted space cleanup is done, and doesn’t relate to restoring what’s deleted from the backup. Or if the file is really old, a version may still exist that’s close enough after much time. Trimming in the middle wonders if a new file that you created then deleted was really all that important, Setting a maximum age, for example, will give you that long after deletion to realize you want file back. Having things fall off the end or get trimmed out of the middle only matters to recovering the form then. ![]() You might have seen caveats in forum posts that thinning means that a short-lived file or version in no other version will no longer be available as a file version if the whole-backup version it’s in got deleted. File presence (or not) gets similarly versioned. Anything that continues continues, otherwise the idea of versioned backups wouldn’t make much sense. Deleting first version means you lose things (perhaps a file version) only available in that version. A file might be the same, or might change.īoth totally and partially the same files use deduplication, so that only new blocks need be uploaded.īlocks are not deleted until they are used by no versions. That’s a lot, so before heading into small corrections, let me hit what I think is the major worry.Ī backup version is the files as they were seen at backup. So now I will have to figure out what I actually need. When it comes to backup sets, the individual files usually are more important than the state of the whole set, but not always. So which is more important, the history of the whole configuration or the history of its individual files? In VCS, the configuration always is more important. In Git, the version of a configuration is the primary object, and if one needs at all to see the version history of a file (as a tree or some such presentation), it can be derived from the history of the configuration that contains the file, but the derivation process is not always unambiguous. This is where Linus Torvalds turned the tables quite completely. This derivation order has been traditionally motivated by performance aspects, but is often incomplete or otherwise flaky. The difference between Git and all its predecessors is that the traditional VCS tools hold file versions as the primary objects and derive the history of a configuration from file versions. I am just explaining where I am coming from I have a long history with coding and VCS systems. I possibly miss the reference given, but if you consider a configuration to be conceptually like a backup versionīackup system is not a VCS, and I am not trying to equate them in any way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |