how to better verify backups to catch restore errors?
35 views
Skip to first unread message
cubit
Jun 21, 2017, 4:47:31 PM6/21/17
to Qubes Users
Is there a better way to verify that the qubes based backup succeeds?
I discovered today that, while I backup all AppVM and TemplateVM in one time (via GUI), the backups created going back to February all consistently fail to restore one particular appVM,,,,
Yesterday I needed a clean laptop for a travel so I did a full backup and then removed my "storage" AppVM that contain all my documents as well I delete 2 other AppVM, "gpg" and "chat". Can you see where this go......?
Today I go to restore the deleted AppVM via GUI. "gpg" and "chat" restore perfect but "storage" gives error even though when I veryify the archive it is ok :((
ERROR: [Errno 2] No such file or directory: u'/var/tmp/restore_LtT4Jk/vm1'
*** Skipping VM: storage
-> Done. Please install updates for all the restored templates.
-> Completed with errors!
I try using "qvm-backup-restore -d sys-usb /path/to/backup/qubes_backup_time storage --debug" to see if there are more details. It fails too and no much details are extra See attached restore_errors.txt where it try vm17
What is interesting is that for some reason it is trying to restore vm17 which is not my "storage" vm based on the qubes.xml in the same directory. My "storage" vm should be 1.
I was able to do "emergency backup recovery" on files in vm1 directory and as hoped, all my "storage" appVM files were in there.
I had to go to backups from February before I could find one that would restore "storage" appVM from GUI or qvm-backup-restore
Some questions
- how can I better veryify backups working?
- why does it seem qubes is getting confused about appVM qid on restore?
- at top of restore_error.txt file it says only 1MB to restore, even when AppVM is 1.8GB is size, why size difference?
- is there anything I can do to compare the good backup that restores via gui and any of the many broken backups to see what went wrong?
- how can I be sure this qid mixup won't happen again?
I discovered today that, while I backup all AppVM and TemplateVM in one time (via GUI), the backups created going back to February all consistently fail to restore one particular appVM,,,,
Yesterday I needed a clean laptop for a travel so I did a full backup and then removed my "storage" AppVM that contain all my documents as well I delete 2 other AppVM, "gpg" and "chat". Can you see where this go......?
Today I go to restore the deleted AppVM via GUI. "gpg" and "chat" restore perfect but "storage" gives error even though when I veryify the archive it is ok :((
ERROR: [Errno 2] No such file or directory: u'/var/tmp/restore_LtT4Jk/vm1'
*** Skipping VM: storage
-> Done. Please install updates for all the restored templates.
-> Completed with errors!
I try using "qvm-backup-restore -d sys-usb /path/to/backup/qubes_backup_time storage --debug" to see if there are more details. It fails too and no much details are extra See attached restore_errors.txt where it try vm17
What is interesting is that for some reason it is trying to restore vm17 which is not my "storage" vm based on the qubes.xml in the same directory. My "storage" vm should be 1.
I was able to do "emergency backup recovery" on files in vm1 directory and as hoped, all my "storage" appVM files were in there.
I had to go to backups from February before I could find one that would restore "storage" appVM from GUI or qvm-backup-restore
Some questions
- how can I better veryify backups working?
- why does it seem qubes is getting confused about appVM qid on restore?
- at top of restore_error.txt file it says only 1MB to restore, even when AppVM is 1.8GB is size, why size difference?
- is there anything I can do to compare the good backup that restores via gui and any of the many broken backups to see what went wrong?
- how can I be sure this qid mixup won't happen again?
Andrew David Wong
Jun 21, 2017, 11:58:38 PM6/21/17
to cubit, Qubes Users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
You can use the "verify-only" restore option (available both in Qubes
Manager and on the command-line) immediately after creating a backup.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJZS0BjAAoJENtN07w5UDAwKnQQALo2uYmdbW6zcBTmYEYC2QuV
W+zgp+pT0S/SXK7qqG5Qw5o3N2y104eK95DvKK0ZyBC/UIbnsYO4u77oECC1CTsx
r+kpkr7cslNMsnkleUPk6ahwutZZg/eJ6E57w2kPGcDJdBh8ys2i8ubHGM2hft85
9jOAcbjUP5X9COVO4TtCK3JF67R9VpmemXSgNE8BlVFsmaqdncgSO/RfjTx/+Oov
QuborHaz4GRFrw6ObAoRlObsrF+QHqMj+zQVmUUXD+6IT+SRSUi/J6NX0WHJbxgf
Vzp1cfZEDgdHGEY718yyiwDxhYk6BofQQ5on0E8ogJfucdWQgCBrW3uxnvfovxcM
Z41Khz4vtHtEpOiWApNAYT2XxFQRGZ/1XArIE7UbU7T0f9d9mPf31SxyYr9aHUER
l0izY7UZ0bIjRjr1vAVDgSNep9drO25wWQ/ia/5M0NHIy+xknRyA00OF9q2Cf2r0
uZdlJHuFi9htyI6Wd925ajP07LOfPxR8RMlS5+SLHkYF90pQkg4XdSo0wf3XBopc
gO0+ijEqYOzZtyoaUARwbpxV7tLOPsa/AvJgJthphB6UgtMDUoio42FYMUbRmqXt
VLK0L/7Xj8fvQzFHRig6xMOYFvLjEml+zR6dYzNQK2S2uklZdqFJkT6I4fWoEDZB
4A594AjYXaLPsaBgDmSw
=gDtA
-----END PGP SIGNATURE-----
Hash: SHA512
Manager and on the command-line) immediately after creating a backup.
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJZS0BjAAoJENtN07w5UDAwKnQQALo2uYmdbW6zcBTmYEYC2QuV
W+zgp+pT0S/SXK7qqG5Qw5o3N2y104eK95DvKK0ZyBC/UIbnsYO4u77oECC1CTsx
r+kpkr7cslNMsnkleUPk6ahwutZZg/eJ6E57w2kPGcDJdBh8ys2i8ubHGM2hft85
9jOAcbjUP5X9COVO4TtCK3JF67R9VpmemXSgNE8BlVFsmaqdncgSO/RfjTx/+Oov
QuborHaz4GRFrw6ObAoRlObsrF+QHqMj+zQVmUUXD+6IT+SRSUi/J6NX0WHJbxgf
Vzp1cfZEDgdHGEY718yyiwDxhYk6BofQQ5on0E8ogJfucdWQgCBrW3uxnvfovxcM
Z41Khz4vtHtEpOiWApNAYT2XxFQRGZ/1XArIE7UbU7T0f9d9mPf31SxyYr9aHUER
l0izY7UZ0bIjRjr1vAVDgSNep9drO25wWQ/ia/5M0NHIy+xknRyA00OF9q2Cf2r0
uZdlJHuFi9htyI6Wd925ajP07LOfPxR8RMlS5+SLHkYF90pQkg4XdSo0wf3XBopc
gO0+ijEqYOzZtyoaUARwbpxV7tLOPsa/AvJgJthphB6UgtMDUoio42FYMUbRmqXt
VLK0L/7Xj8fvQzFHRig6xMOYFvLjEml+zR6dYzNQK2S2uklZdqFJkT6I4fWoEDZB
4A594AjYXaLPsaBgDmSw
=gDtA
-----END PGP SIGNATURE-----
cubit
Jun 22, 2017, 1:11:28 PM6/22/17
to Andrew David Wong, Qubes Users
22. Jun 2017 03:58 by a...@qubes-os.org:
You can use the "verify-only" restore option (available both in Qubes
Manager and on the command-line) immediately after creating a backup.
That is the problem. I have done the verify and it passes with no error for all of the backup archives that have problems restoring my "storage" AppVM. As I discovered this has been a problem for nearly 4 months worth of backups.
I am trying to find if there is another way to verify backups because the built in method and restorting is failing me at the moment. Or better fix the backup/restore issue
Andrew David Wong
Jun 22, 2017, 10:33:48 PM6/22/17
to cubit, Qubes Users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hash: SHA512
serious bug:
https://github.com/QubesOS/qubes-issues/issues/1577
Just to check: Have you (per my comment on that issue) tried
rebooting, then trying again to verify/restore a backup that should be
working?
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
BlqjH2In+wsnYPRhC6CxbI6ILjYPOFzWclVxt2MlvZdILte/h7iHps8YbPiAELGA
l869ubBbBTrlT8bMzIRR2XTKim+1bZWRCtnBgMwhSxGkDxCcdZqc4klO0hy0br4D
6vSsBbIYF+ZLrpkvEvBVSZJALxFACiv8gAvgQ4SdgW3ermPg2J9+wsAQ7bEw2wj4
jXjx47l0rHmqtQ53mM76S1vJ+kt7CB0QffBY7KJh0Iz9ELbyrhH+V3kjt+aAF3/I
nNLVpHu0mAwmlpSbObfa/3NJghw2oOW6b0BeE90bGfLIbARL6XEMzcxvINZUz1rs
b74n/A96nhqaqqwS9yzbkPYgdaUkZfruWROsAz4oQeHInrdMxdH6Cdn0j2/1flp+
ILTgSzuAoQh+lZdc0bJ6wl2OEDVNUrc65Tjy2PukhV1mqnze2d9pGJ7DgdMWiRFe
zOZunetX2umt4KDHbLM5gbnvVHitUZCnFp4FBJmKKt7JN30Ogs0evyVLCabop009
0a/BAFSTxfoU5O3yzUbC4vaaDJNlIy440qegUbd480ZhdJBgXdtDFdExX9TZreOS
65Ml4oKIwkgKFCPhHwFarRigIurXJNBQqtzlyxUnsNOO32RuHLh/U3DIcV70cnp2
Kl3HGEgguNASpPxx0OI4
=C1LD
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages