Hi,
I'm testing SnapCreator 3.6.0 to perform backups for my KVM based virtual machines.
To support rapid clones, I have set up two qtrees on the same volume. Virtual Machines run on /vol/nebula/0 (qtree), and my templates are on /vol/nebula/1 (qtree).
The problems I have are the following:
- When I try to quiesce SnapCreator, it can't find the virtual machines, because I keep the "xml" file under /vol/nebula/0/vm<name>/deployment.0.
As far as I can see, SnapCreator only uses the VM information to auto-populate the volumes that should be backed up.
How can I disable auto-discover and add the volumes manually?
- To fix the previous issue, I just create symbolic links of the xml files to /etc/libvirt/qemu.
Unfortunately, my installment adds two slashes to the path of the virtual disk (/var/lib/one//datastore/0/one-20/disk.0), but the path is perfectly valid.
The problem here is that SnapCreator is not able to resolve the path to storage device.
I would suggest that it should sanitize the path before trying to match the mount points.
- After I fixed all the paths, SnapCreator still does not work.
SnapCreator is able to find the storage controller and path, but is not aware of the qtree. So, instead of using /vol/nebula, it uses /vol/nebula/0 and fails.
This could be fixed by always limit the path on the storage to a depth of 2 (maybe when it starts with /vol/), or allow users to override auto discovery.
Are there any workarounds for these issues?
As this is a community release, am I able to access the sources for the KVM plugin?
Thanks.