Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upImprove backup restore and verification to check whether VM data is missing #3498
Comments
andrewdavidwong
added
enhancement
C: core
P: major
labels
Jan 27, 2018
andrewdavidwong
added this to the Release 4.1 milestone
Jan 27, 2018
andrewdavidwong
referenced this issue
Jan 27, 2018
Closed
qubes-backup-restore does not restore dom0 from 3.2 backup #3467
awokd
referenced this issue
in QubesOS/qubes-doc
Jan 27, 2018
Merged
backup-restore Update for 4.0 #534
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Mar 29, 2018
@marmarek - I'd like to know if you consider this a dom0-only issue?
Currently restore will cycle through all VMs contained in an archive by default, and I think that if any chunk from a VM is missing then the encryption and/or compression layers will report an error. Even the inner tar command should report an error on its own if something is structurally missing (although its other layers that validate data).
dom0 is currently the only VM where the inner tar isn't checked during --verify-only. On R4.0 it still has to successfully decrypt, however.
tasket
commented
Mar 29, 2018
|
@marmarek - I'd like to know if you consider this a dom0-only issue? Currently restore will cycle through all VMs contained in an archive by default, and I think that if any chunk from a VM is missing then the encryption and/or compression layers will report an error. Even the inner tar command should report an error on its own if something is structurally missing (although its other layers that validate data). dom0 is currently the only VM where the inner tar isn't checked during --verify-only. On R4.0 it still has to successfully decrypt, however. |
andrewdavidwong commentedJan 27, 2018
In #3467 (comment), @marmarek wrote: