Displaying 2 results from an estimated 2 matches for "nexcloud".
Did you mean:
nextcloud
2020 Jan 05
3
(no subject)
...the
following
command works for all of them bar one:
# virsh snapshot-create-as --quiesce --no-metadata --domain myvm myvm-state
--diskspec vda,file=overlay.qcow2 --disk-only --atomic
The only exception is this one vm, which has two disks as two separete
qcow2 files: vda and vdb. Vdb contains my nexcloud data, resides on a
btrfs subvolume, and a daily snapshot of this subvolume is taken by a
cronjob
by the host machine. Therefore, I do not want to include it in the
snapshot taken by virsh, and therefore I did not include vdb as a
separate --diskspec item, and used the same command indicated above....
2020 Jan 06
0
Fwd: (no subject)
...if you use a qemu released in at least last 5
> years as the snapshot is always atomic if the qemu supports the
> 'transaction' command.
>
> >
> > The only exception is this one vm, which has two disks as two separete
> > qcow2 files: vda and vdb. Vdb contains my nexcloud data, resides on a
> > btrfs subvolume, and a daily snapshot of this subvolume is taken by a
> > cronjob
> > by the host machine. Therefore, I do not want to include it in the
> > snapshot taken by virsh, and therefore I did not include vdb as a
> > separate --diskspec...