XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. fluffy-bunny
    3. Topics
    F
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 21
    • Groups 0

    Topics

    • F

      Get VM from <ID>.vhd from Storage-Record

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      7
      0 Votes
      7 Posts
      2k Views
      T
      @fluffy-bunny Use this to get your VBDs from each VM xe vm-param-get param-name=VBDs uuid=<vm-uuid> Then to get the name of each VDI file use this xe vbd-param-get param-name=vdi-uuid uuid=<vbd-uuid> But as olivier said, it is much easier to just use XO's disk view of the VM you want, then use the "copy" button to copy its VDI name.
    • F

      Memory Usage wouldn't be displayed in XOA

      Watching Ignoring Scheduled Pinned Locked Moved Solved Xen Orchestra
      8
      4
      0 Votes
      8 Posts
      1k Views
      olivierlambertO
      So yes, it was the service not started properly, so we didn't get the info into XOA You are welcome, enjoy it!
    • F

      How to save Statistic from XOA when rebooting the XCP-NG Nodes?

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      6
      0 Votes
      6 Posts
      276 Views
      olivierlambertO
      It should be the same result on XCP-ng Center: it uses RRDs files stored on the host. Why do you continue to talk about the after the reboot? You mean after the upgrade, right? RRDs are preserved after a reboot If you do a yum update, those stats should be in theory preserved. If it's not the case, try to diagnose why, by comparing behavior between XCP-ng Center and XO. If it's not the same, then it's a client issue. If it's the same, then it means a version upgrade (yum or ISO) won't preserve RRDs. If you really want long terms stats for "real production" usage on long term, I strongly suggest that you think to store them in a real time series database, like Prometheus or so.
    • F

      No Statistics in XOA after Rebooting our XCP-NG Nodes

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      6
      1
      0 Votes
      6 Posts
      791 Views
      olivierlambertO
      Nothing. You should have the stats visible in live (post-upgrade). That's it. If you don't, it might be because your nodes are behind a NAT.
    • F

      Get an 'Disconnected' Information under the 'XOA' Icon

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      3
      1
      0 Votes
      3 Posts
      557 Views
      DanpD
      That's "normal" if you are running XO (from the sources) and not XOA (the pre-built appliance)
    • F

      How to detect when Backups fails in XOA!?

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      4
      0 Votes
      4 Posts
      575 Views
      olivierlambertO
      This is a 3rd party container not validated nor endorsed by XO devs. We don't know what's inside, if you have questions on it, ask on the Github repo of the maintainer Backup reports will answer your initial question/requirement (reports can be sent by email, Slack etc.) There's also a Nagios plugin, or you can use XO API to make request to be support in any software of your infrastructure Monitoring a Docker container is outside scope of XO, I would suggest to ask Docker community. Regarding XO and how backup are done, any fresh XOA deployed (or from the sources) will be able to find all the previous backup done by an old XOA, because we store every info on the remote.
    • F

      Run an backed-up VM from an NFS-Share

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      7
      0 Votes
      7 Posts
      818 Views
      olivierlambertO
      The best option is to use Disaster Recovery, or both DR with your current backup. It's the easiest way. Please watch the video I posted.