So i guess the "pivoting" was what i wanted to do. Now it looks like this: virsh domblklist polar-bear2 Virsh blockcommit polar-bear2 vdb -verbose -pivot -active So after i ran virsh blockcommit polar-bear2 vda -verbose -pivot -active I came across this article:Īnd after some hesitation i thought i had backups now and could try it.
So after I examined the XML in the step described above, i came to the conclusion to search the internet for "Backingstore". how do i get this back to one image? UPDATE2 - solution? The nextcloud_data.backup_recover image is only ~2.5GB in size, the original one /home/user/vms/nextcloud_data_2.img is 16GB though. Vdb /mnt/sda3/nextcloud_data.backup_recover The XML of polar-bear2 now looks as follows: Īt least this is seems okay now: virsh domblklist polar-bear2 The original one is in paused while the newly created one runs on the recovered images + copies of the old images. virsh snapshot-list polar-bearĪfter following the solution from DanielB below, i have now two VMs. I guess something went wrong when the snapshots were deleted?Ĭurrently no snapshots are configured for this machine. The VM runs fine though and it even rebooted without any issue.īut i'm a bit afraid i'm running into some horrorful scenario soon. Ls: cannot access '/home/user/vms/*.backup': No such file or directory However, these files do not really exist at this palce.
Edit: see solution to my problem below in Update2.Īfter playing around with some backup script i have the following situation virsh domblklist polar-bear
0 kommentar(er)
