@dcskinner @olivierlambert You can read key/values from the xenstore, and write some (from VM to outside), but you cannot write values "in live" from outside the VM to the inside. It is, but XAPI doesn't provide a interface for it. do the guest tools quiesce the filesystems before snapshotting? Tools are aware of a snapshot so you don't have blocks in flight. do the guest tools quiesce the filesystems before snapshotting? Guests kernel are aware, as it is them that are performing a "suspend" on toolstack request (thus quiece filesystems); although "tools" can only observe that the system has been suspended after the fact by measuring side effects, and not orchestrate it. It's because suspend/resume operation doesn't come from "guest tools" actually, but instead from the kernel drivers. So userland tools has no say on it.

@rzr No I did not customize anything related to rsyslog on XO / XCP-ng side. No tweaking of rsyslog config file(s) or similar. I just setup a graylog server, enabled the syslog udp input there and configured rsyslog via Xen Orchestra like so: [image: 1769109214059-1b446ebe-7bee-492b-aacf-43531e7d050c-grafik.png] I consider this the most basic setup. Also: AFAIK there are no UI options for rsyslog custom rules. Enabling it and setting IP address/port is basically all that can be done. I read that Vates recommends to not fiddle with config files on dom0 and view XCP-ng as an appliance. So maybe custom rsyslog config does not need to get considered as long as no new GUI features for that are planned.

Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

@florent Thank you, I will try this.

@florent I think you meant it was locking the xoa via .tar.gz but not via .zip which seemed to be the case Yeah I just decompressed the restored .zip and checked number of files and size via ncdu, result: "Total disk usage: 194,5 MiB Apparent size: 193,1 MiB Items: 613" In case I can provide more information for investigating this issue, please let me know. Thanks and best regards

@guillemrebull in your xo logs, you should have a line like nbdkit logs of ${diskPath} are in ${tmpDir} could you copy here the file in tmpDir ( something like /tmp/xo-serverYYYY/stderr ) ?

Does it work as you wanted now? If yes, probably something we can put in our official doc! Ping @thomas-dkmt

@mpiton thanks for sharing docs, the crucial part was openssl rand -hex 32 my password was too simple and that's why i got :"Query authentication does not match server setting" error after setting 32 characters password i got my metrics, in both http://localhost:9004/metrics and http://<xo-ip>/openmetrics/metrics