Backup option to remove a leading path prefix
Output of `restic version` -------------------------- ``` restic 0.9.3 compiled with go1.11.1 on linux/amd64 ``` What should restic do differently? Which functionality do you think we should add? ---------------------------------------------------------------------------------- It would be helpful to have an option to `restic backup` that says "strip this leading path from the paths of all backed-up files." For example, `--backup-root /some/path`. This would have the following effects: * A file `/some/path/to/file` would be stored in the snapshot as `/to/file`. * This file would also have its metadata check performed against `/to/file` in the parent snapshot. * You are not permitted to specify files/directories to `restic backup` that do not begin with this prefix. (I think this may be related to #1376.) What are you trying to do? -------------------------- One of our backup scripts is run on a system with many running services that a cannot stop. These services guarantee that recovery is possible from a specific point in time (e.g. they do enough journaling to get their data back in a consistent state following a power cut). However, restic backups are not atomic; therefore, restic backups break the recovery guarantee from the service. To fix this, we: 1. Take an LVM snapshot of `/`. The snapshot is an atomic block-level copy of the entire volume. 2. Mount the LVM snapshot under `/mnt/backup-snapshot`. 3. Run the restic backup against `/mnt/backup-snapshot`. 4. Un
Posted by cdhowie on Nov 16, 2018, 8:19 PM
Tags
Related issues
- Custom games stuck on "finding server" for all european servers
- Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
- Forza Horizon 6 (2483190)
- Turn off integrated browser for default
- Weekly updates are too frequent
- [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Sysadmin)
Custom games stuck on "finding server" for all european servers
Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
Forza Horizon 6 (2483190)
Turn off integrated browser for default
Weekly updates are too frequent
[BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)
Add gemini-3.1-pro-preview
[TF2] Feature request: Bring Back Quickplay
Backup option to remove a leading path prefix
Output of `restic version` -------------------------- ``` restic 0.9.3 compiled with go1.11.1 on linux/amd64 ``` What should restic do differently? Which functionality do you think we should add? ---------------------------------------------------------------------------------- It would be helpful to have an option to `restic backup` that says "strip this leading path from the paths of all backed-up files." For example, `--backup-root /some/path`. This would have the following effects: * A file `/some/path/to/file` would be stored in the snapshot as `/to/file`. * This file would also have its metadata check performed against `/to/file` in the parent snapshot. * You are not permitted to specify files/directories to `restic backup` that do not begin with this prefix. (I think this may be related to #1376.) What are you trying to do? -------------------------- One of our backup scripts is run on a system with many running services that a cannot stop. These services guarantee that recovery is possible from a specific point in time (e.g. they do enough journaling to get their data back in a consistent state following a power cut). However, restic backups are not atomic; therefore, restic backups break the recovery guarantee from the service. To fix this, we: 1. Take an LVM snapshot of `/`. The snapshot is an atomic block-level copy of the entire volume. 2. Mount the LVM snapshot under `/mnt/backup-snapshot`. 3. Run the restic backup against `/mnt/backup-snapshot`. 4. Un
Comments (0)
No comments yet. Start the discussion.