forked from TrueCloudLab/restic
2b88cd6eab
SaveTree did not use the TreeSaver but rather managed the tree collection and upload itself. This prevents using the parallelism offered by the TreeSaver and duplicates all related code. Using the TreeSaver can provide some speed-ups as all steps within the backup tree now rely on FutureNodes. This can be especially relevant for backups with large amounts of explicitly specified files. The main difference between SaveTree and SaveDir is, that only the former can save tree blobs in which nodes have a different name than the actual file on disk. This is the result of resolving name conflicts between multiple files with the same name. The filename that must be used within the snapshot is now passed directly to restic.NodeFromFileInfo. This ensures that a FutureNode already contains the correct filename. |
||
|---|---|---|
| .. | ||
| archiver.go | ||
| archiver_test.go | ||
| archiver_unix_test.go | ||
| archiver_windows_test.go | ||
| blob_saver.go | ||
| blob_saver_test.go | ||
| buffer.go | ||
| doc.go | ||
| file_saver.go | ||
| file_saver_test.go | ||
| scanner.go | ||
| scanner_test.go | ||
| testing.go | ||
| testing_test.go | ||
| tree.go | ||
| tree_saver.go | ||
| tree_saver_test.go | ||
| tree_test.go | ||