Thanks for the guidance, that's all I need.
It's all working now.
the error disappeared with commit efc3f45ef63e4ee7bb5efeca063328faafade9bb
I don't think we're on the same page.
The scenario is like this:
The real VM is in another site and has two disks (system and database).
I have a copy of it, with the help of CR, on my site.
From the copy on my site I want to use only one disk (database).
The idea I started from is to make a copy on the whole VM and then use only disk 2.
Only for this copy I need 20 hours + and CR is done every 2 hours.
All I want now is to disable CR job when I make the copy to not break the CR.
And after I finish the copy to enable the CR job.
For now, as I said, I'm taking the following steps:
All i want is to find a way through xo-cli to be able to temporarily disable this CR job.
I use continuous replication on a production VM.
This is done over internet, it is slow.
Local I have this copy of VM, but I want to make a copy of copy.
And if continuous replication is enabled when I made a copy, I get a continuous replication brake chain if it starts when copying is in progress, as you said.
On the xo-cli --list-commands I couldn't find a way to disable this continuous replication and when I finish to enable again.
For now I disable the sync on web gui manually , start the copy and then enable again.
And now wat I want is to automate this process because it happens periodically.
And all I missing is the right command line to disable and enable this continuous replication task on XOCE
I didn't see it in the demon's help of xo-cli.
I want to use xo-cli and by connecting on ssh to XOCE to disable it the certain task (continuous replication (CR) of an VM and after I finish the rest of my task to enable the task again.
The scenario is as follows:
I have a CR that syncs every 2 hours from another site over internet.
Locally I want an certain disk of this VM (the CR vm) to be copied to be used in another VM.
I did a bash script identifying the VM (the CR one) and HDD I wanted to copy but couldn't figure out how to turn off (disable) CR syncing on XOCE that handle the continuous replication sync.
This copy takes 20 hours + even on 10Gb LAN, and during this time I will have at least 10 CR syncs that will fail and at the end (when the copy ents) will make a full one, which I do not want.
I what to be able to deactivate and activate this button but over xo-cli
Yes, I first noticed this with commit ec81e90153b655cf4a25530766f0a7b81a4428a9, and and I downgrade step by step until eee4981d4c9df6a1662d5272591b7552e46a119d .
I'm not trying to export a snapshot, I export VM that is allrady running by accessing the button below.
In the first post I took those photos to show you that the snapshot it starts but gives an error on export.
When i want to export a vm I have an error and export is not happen, this happens whether it is with compression or not
this happens starting with commit 6aa5ec6eb69cc286ee639f208703a9066878b31c
The commit eee4981d4c9df6a1662d5272591b7552e46a119d is ok
The snapshot is ok but when download shod start I get this error
Is there any option to set for timeout value?
I say this because, monitoring the process, everything seems to be going well until the moment when it starts to check the free space.
XCP-NG is 8.2 up to date, the disk on which the VM is it is formated as local ext.
The connection to the backup server is on NFS on the LAN at a speed of 1Gb.
On the iotop it seems that the space check goes with speed 650Gbits +.