"tahoe backup --prefix": override pathname root for snapshots #632
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#632
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been perusing the LVM documentation, looking at the "snapshot" feature, which of course could be used for easy coherent backups (to avoid the concern that someone will change a file while you're backing it up, thus getting neither the old version nor the new finished version). But the current implementation of tahoe's backupdb uses
os.path.abspath
as the lookup key. So if we were to snapshot, say, /home into /mnt/home-snapshot-TIMESTAMP before running 'tahoe backup' against /mnt/home-snapshot-TIMESTAMP, the backupdb filenames would be completely different than the previous day's /mnt/home-snapshot-OLDTIMESTAMP.So the useful feature would be to give 'tahoe backup' a
--root
or a--strip-prefix
argument, which would tell it to remove some portion of the absolute pathname (and perhaps replace it with some other string) before doing the backupdb lookup. This would allow /mnt/home-snapshot-TIMESTAMP/foo to be compared against the previously-uploaded /mnt/home-snapshot-OLDTIMESTAMP/foo .By the way, I had a good idea for a technique to avoid missed or inconsistent backups of a file at the cost of having delayed (even indefinitely delayed) backup of that file. It is written in this message:
http://allmydata.org/pipermail/tahoe-dev/2008-September/000809.html
I do hope that the makers of backup tools (Brian, Shawn, Francois?, ?) think about this, because the failure modes of the naive approach are rare and ugly, and my technique to avoid it doesn't seem too complicated.
Of course, what you really want is something much more sophisticated, such as a file-system-wide cheap snapshot. NTFS has something along those lines -- Volume Shadow Something Or Other, and of course ZFS is really good at that, and hopefully someday BTRFS and others will be. But for now, please consider whether my technique described in that mail will work.
#848 was a duplicate of this one, merging them.
backupdb: override pathname root for snapshotsto "tahoe backup --prefix": override pathname root for snapshots