-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
No way to exclude disks #2
Comments
its some time since ive used it as i currently have no test setup. The include swich should work as expeced, does "vda" match the virtual disks target name in the xml configuration? According to the source, im checking for the target name:
one would need the vm XML configuration to check why it doesnt skip the disks. |
abbbi, I believe "vda" does match
|
can you post complete output of your command? Does the "Skipping disk:" logline appear at all? |
the domain configuration iss missing the required incremental flag like described in the README: |
Can you try the version in branch issue2,it should now automatically exclude cdrom and raw devices. |
the domain configuration iss missing the required incremental flag like described in the README: |
Ok, I just created a new, plain vanilla, centos7.0 VM to try to replicate the problem and I still got that last error message.
Then I remembered, I forgot to add "<qemu:add capability='incremental-backup'/>" like I did before.
and I'm trying to figure out why I could before and now I can't. Something new I've noticed with Fedora 33 is that it automatically installs updates every time I reboot. And I see that schema file got updated just a few days ago:
|
hm.. not sure, but maybe things have changed now with more recent libvirt versions, it seems to be enabled by |
hi, i tried on centos8 with the latest advanced virtualization stream and i still need to add the XML definition,
so the schema applies! |
hi again, i have a new test setup and was able to fix a few things in the current master branch:
i see only vdb is backed up:
Anyway, try the latest master version, it should fix your issues. |
Yes indeed. All is working now. Thank you! |
An interesting project. I tried virtnbdbackup on a CentOS 7 VM on a Fedora 33 host. The VM has a small, QCOW2 system disk and a large, raw storage disk, and a CDROM drive that is unused, but it got created by default. I only wanted to back up the system disk, vda.
At first it couldn't get past the CDROM drive, sda:
ERROR:root:unsupported configuration: disk 'sda' has no media
I attached an iso file to the CDROM drive and then got:
ERROR:root:unsupported configuration: disk 'sda' is empty or readonly
So I deleted the CDROM drive and then it couldn't get past the raw storage drive, vdb
ERROR:root:unsupported configuration: checkpoint for disk vdb unsupported for storage type raw
So I deleted the vdb disk device, and only then it succeeded in creating a backup of the system disk, vda.
I found in the code the "--include" commandline switch:
parser.add_argument("-i", "--include", default=None, type=str, help="Backup only disk with target dev name specified")
That seems like just what I needed.
[root@oplx7010 2TBpart]# virtnbdbackup -d centos7.0 -i vda -l full -o centos7.0.virtnbdbackup
But I still failed the same way with the same messages. The "include" switch had no apparent effect. It did not result in the other disks being ignored as I would have expected.
Thank you.
Richard Ketcham
The text was updated successfully, but these errors were encountered: