I have, what is hopefully a final update to this issue(s).
we upgraded to xoa version .99 a few weeks ago and the problem has now gone away. we suspect that some changes were made for timeouts in xoa that have resolved this , and a few other related problems.
@olivierlambert the 3 truenas servers are very bored 
we be lucking to be hitting 10% of there abilities even during the backups.
i think i have stumbled across something that maybe a bug or the cause:
lets say we have 5 servers, VM getting this error during backups is running on server3, When this happens we power it down on server3 and clear the stuck tapdisk connections a log entry shows up saying a snapshot link on server5 was also cleared....
example: "Cleared RW for 7d213264-1f89-488f-b273-eb91c186eaab on host 14c98969-ae12-4d7f-9c42-d7656aae01e5 on server5"
... but the VM was running on server3.....
so HERE is what i think is happening... just a theory... I think the load balance plugin is moving VMs around during the backup process. could that be possible?? i feel based on what i am seeing this could be the cause.
This problem is back with vengeance. after almost a year of no issues, we have upgraded to version 109.2 of XOA and boom... probably is back
XCP-NG servers are on 8.2.1 May 6th update
we get this following error in XOA
Error: SR_BACKEND_FAILURE_82(, Failed to snapshot VDI [opterr=failed to pause VDI 7d213264-1f89-488f-b273-eb91c186eaab], )
cant make snapshots of the effected VM anymore...
manual snapshots we get same error:
SR_BACKEND_FAILURE_82(, Failed to snapshot VDI [opterr=failed to pause VDI c51f22e2-ba5c-413b-8afc-9208a2b944ef],
but there is NO issues with the SR.
failed 17 backups last night,
failed 3 backups tonight.
across 3 different storage arrays
all those VM's we had to shut down and fix.
tapdisk connections to the disk have to be manually killed.
we will double check all our interfaces again but i suspect it will be the same as last time:, no errors on networking or storage side.
something has changed, reverted.
I got this figured out...
the xcp-ng-updated packages for netdata-ui DO NOT work with xcp-ng, as per my oringial post.
netdata is getting upted by normal xcp-ng updates
this new version does not work , VM's no longer listed.
steps to remove and put on orig version
yum remove netdata-ui -y
yum remove netdata -y
#you have todo this as well or old version wont install
#yum leave files in /usr/share/netdata/ that blokcs installing 1.19
rpm -e netdata-data-1.44.3-1.2.xcpng8.2.noarch
rpm -e netdata-conf-1.44.3-1.2.xcpng8.2.noarch
yum install netdata-ui-1.19.0
#run next line or manualy type it in, you do you
echo "exclude=netdata*" >> /etc/yum.conf
after this, we have version 1.19 installed again that actually works with XEN xcp-ng
I can confirm this as well
several new ubuntu 24 vm's with LVM having this problem. I thought i was going crazy
existing debian 10,11,12 VM's using LVM are not effected
vm's not using LVM are not effected.
Current version: 5.106.4
Mirror Incremental backup task
bug: proxy field cannot be changed back to empty if previously saved with a proxy
I cannot change task from using a proxy to NOT using a proxy.
changing config from :
Proxy
source via proxy
target via proxy
TO:
NO proxy
source
target
result:
error seems like you cant change the proxy value from being filled in to being empty.. however you can make new tasks with this field being empty.
only way i can get around this to re create the back task from scratch.
all proxies and XOA can talk to the remotes in play
Thanks
hello
running xcp-ng version 8.2.1 build date 2025-05-07
restart of node has been done
netdata-ui
version 1.19
release 6.xcpng8.2
from xcp-ng-updates repo
netdata
version1.44.3
release 6.xcpng8.2
from xcp-ng-updates repo
confirmed following also installed
xen-dom0-libs-devel
yajl-devel
xen-devel
i have removed and reinstalled netdata-ui as well
this was working fine before but sometime in the last few months , maybe when netdata updated to the versions above and the interface all changed, VM's are no longer visible in netdata
use to be a giant list of VMs here,
this is happening on all my xcp-ng servers, not just the one. they are all at the above mentioned xcp-ng version and netdata version.
anyone else experiencing this? have any suggestions on whats going on, why the VM's are not showing up in netdata anymore on any of my hosts?
Hi,
last night we had a couple of vm's in a MIRRORING of delta backups task fail. 3 VM's did not mirror for reasons that do not matter for this bug.
when we corrected the issue that caused them mirroring fail we went into XOA and pressed the button to just restart the tasks for the failed VM's only... however OXA decided to redo the entire mirror task and sync EVERY vm on the src backup location.
clicking this to restart just those 3 vm's
caused this to happen... it re synced ALL of them, not just the 3 that failed
XOA version: Current version: 5.103.1
i am assuming this is not working correctly?
I would like to ask a followup question to confirm.
so IF using sequences, we should disable the backup tasks on the overview tab?
I have, what is hopefully a final update to this issue(s).
we upgraded to xoa version .99 a few weeks ago and the problem has now gone away. we suspect that some changes were made for timeouts in xoa that have resolved this , and a few other related problems.
Just an update on this:
we made sure all our server times were synced. issue happened again the next run.
just for shits and giggles we restarted toolstack on the all the hosts yesterday and the problem went away. no issues with the backup last night. maybe just a coincidence, we are continuing to monitor.
we also noticed that even though this CHOP error is coming up, snapshots are getting created