New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-backup can create broken backup archive #902

Closed
marmarek opened this Issue Mar 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by marmarek on 18 Sep 2014 23:47 UTC
Because of tar bug, some VMs cannot be backed up correctly. This affects:

  • every VM, whose root.img/private.img is at least 50GB and have really scattered data (so there is a lot "holes" in the image). Concretely, description of such holes is larger than 100MB (info about one hole use 24 bytes),
  • some standalone/template VMs, whose private.img/root.img (used) size is about multiple of 100MB, and description of the holes in the other image is at least 3MB; this doesn't affect every such VM, only those, where root.img/private.img is such placed in dom0 filesystem, that the first one is the one of N*100MB size.

It looks like it isn't fixable without changing tar archive format, so the solution would be to change our backup format (to not use multi-volume tar feature).

Migrated-From: https://wiki.qubes-os.org/ticket/902

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 18 Sep 2014 23:52 UTC
Because of proximity to R2 final release, we've decided to not change backup format just before the release. Instead we've implemented #863. And made restore process more defensive, namely do not fail when archive of one VM is broken.

If someone encounter this problem (hopefully during backup verification, not a real need to restore the backup...), one can backup such a VM manually, simply copying its root.img/private.img. Then during restore, replace restored (broken) files with those copied manually.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 18 Sep 2014 23:52 UTC
Because of proximity to R2 final release, we've decided to not change backup format just before the release. Instead we've implemented #863. And made restore process more defensive, namely do not fail when archive of one VM is broken.

If someone encounter this problem (hopefully during backup verification, not a real need to restore the backup...), one can backup such a VM manually, simply copying its root.img/private.img. Then during restore, replace restored (broken) files with those copied manually.

@marmarek marmarek added this to the Release 2.1 (post R2) milestone Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by marmarek on 28 Sep 2014 02:15 UTC

Member

marmarek commented Mar 8, 2015

Modified by marmarek on 28 Sep 2014 02:15 UTC

@marmarek marmarek assigned marmarek and unassigned rootkovska Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment