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-restore won't verify data when VMs already exist in system #3303

Closed
tasket opened this Issue Nov 12, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@tasket

tasket commented Nov 12, 2017

Qubes OS version:

R4.0-rc2


Steps to reproduce the behavior:

qvm-backup-restore --verify-only -d backups /mnt/path-to-file

Expected behavior:

The backup file is read and verification results reported.

Actual behavior:

The following is shown almost instantly (thus no verification performed):

app: The above vms will be copied and added to your system.
app: Existing vms will not be removed.
qubesadmin.backup: -> Restoring banking...
qubesadmin.backup: -> Error restoring vm banking, skipping: vm banking already exists
qubesadmin.backup: -> Restoring personal...
qubesadmin.backup: -> Error restoring vm personal, skipping: vm personal already exists

etc...

General notes:

This is with a fresh backup made in R4.

An additional error was shown at the very end:

qvm-backup-restore: error: Invalid file extension found in archive: backup-header

Also, the messaging in 'app:' lines seems inappropriate given that verify-only is used.


Related issues:

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Dec 1, 2017

Another bug inherent to this issue:

Spurious new VMs were created during the verify process. For example, if 'personal' VM didn't exist in the live system but you verified an archive containing a 'personal' VM then a new VM by that name would be created.

The submitted PR should prevent this also.

tasket commented Dec 1, 2017

Another bug inherent to this issue:

Spurious new VMs were created during the verify process. For example, if 'personal' VM didn't exist in the live system but you verified an archive containing a 'personal' VM then a new VM by that name would be created.

The submitted PR should prevent this also.

@tasket

This comment has been minimized.

Show comment
Hide comment
@tasket

tasket Jan 10, 2018

PR was merged.

tasket commented Jan 10, 2018

PR was merged.

@tasket tasket closed this Jan 10, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 11, 2018

Member

Keeping this open for builder-github (unless we know we don't need it tracked for some reason).

Member

andrewdavidwong commented Jan 11, 2018

Keeping this open for builder-github (unless we know we don't need it tracked for some reason).

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 11, 2018

Member

Never mind, looks like tracking works fine even if it's closed.

Member

andrewdavidwong commented Jan 11, 2018

Never mind, looks like tracking works fine even if it's closed.

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