1. Home
  2. Xen Orchestra

Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    451 Topics
    3k Posts
    DustyArmstrongD
    @nikade Sure. I have 2 mini machines running as XCP hosts, decided to upgrade them to newer hardware as they were struggling. I have: XC1 - Brand new pool master on pool XC1 XC2 - Brand new pool slave on pool XC1 XCP1 - Old pool master on pool XCP1 XCP2 - Old pool master on pool XCP2 Installed XCP on both the new hosts, imported to Xen Orchestra, designated the first as pool master, added the second to the pool. Performed updates, did some nominal checks and called them good. Wasn't ready to migrate my VMs yet so powered both off. Came yesterday, I unplugged my old hosts and set them aside, plugged in my new hosts (this is onto my UPS supply) power and network. Plugged in my old hosts to my temporary working area to migrate VMs. Powered everything on (old then new). XO stayed online the whole time, though DNS is on a VM that went down. Only a single host came up (XCP2 - slave of XCP1). XCP1 had to be rebooted 3 or 4 times before it finally came alive but at a big ping delay (4ms, usually <1ms). XC1 and XC2 never came alive, their NICs had physical activity but got nothing. Eventually plugged in a monitor (awkward so didn't do it immediately), rebooted them both and saw no network configuration on either, just empty. Found this thread and decided, as they were basically fresh, I would just re-install and start over. Eventually got everything back. I am assuming based on this thread that XC2 may have come up before XC1 and thus couldn't connect so it obliterated itself. Don't know why XC1 also did the same. During testing I powered both XC1 and XC2 on and off multiple times without this happening, it was only when I powered everything on after moving them that it occurred. Thought I was going nuts or had caused a major network loop somehow.

  • ACLs, Self-service, Cloud-init, Load balancing...

    100 Topics
    832 Posts
    Tristis OrisT
    Ok, my syntax is oudated. resize_rootfs: true growpart: mode: auto devices: ['/dev/xvda3'] ignore_growroot_disabled: false runcmd: - pvresize /dev/xvda3 - lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv || true this one works. final_message. doesn't support any macro like %(uptime) %(UPTIME)

  • All XO backup features: full and incremental, replication, mirrors...

    461 Topics
    5k Posts
    P
    @blueh2o said in Health check scripts. Where is the example?: xen-orchestra/backups/docs/healthcheck example/wait30seconds.sh that would be here https://github.com/vatesfr/xen-orchestra/tree/master/%40xen-orchestra/backups/docs

  • Everything related to Xen Orchestra's REST API

    77 Topics
    583 Posts
    R
    @Pilow tags can work and the path to them is much more succinct. Thanks!

  • Terraform, Packer or any tool to do IaC

    49 Topics
    452 Posts
    J
    @nathanael-h As a further follow up the MCP agents include at minimum:- Pulumi MariaDB Anyway I would really appreciate having an MCP Server which, can be used when writing IaC to provision and configure your customers’ systems. Can it be made available during this year please?
Log in to post
Load new posts
  • D

    XO from source & Netdata

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    D
    @Biggen Ahh gotcha. I’ll check that out
  • D

    Backups to SMB remote failing

    19
    1
    0 Votes
    19 Posts
    5k Views
    julien-fJ
    @Danp The implementation would be very different
  • akurzawaA

    xoa - repair iso SR after host restart

    2
    1
    0 Votes
    2 Posts
    336 Views
    olivierlambertO
    Repair is just replug the pbd. Of course you can do that with XO
  • D

    XO Delta Backup failure

    Solved
    4
    0 Votes
    4 Posts
    649 Views
    olivierlambertO
    Okay thanks for the feedback
  • C

    Problem with restore through XenOrchestra

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    A
    But now release xo-server 5.53.0 backup export concurrency >2 didn't apply. Setting concurrency to 4 or 6. but only 2 tasks works at the same time. Reverted to release xo-server 5.52.1 then 4 and 6 concurrency tasks are shown as expected.
  • bill.gertzB

    XOA won't start HTTPS listen on configured port

    29
    0 Votes
    29 Posts
    11k Views
    julien-fJ
    @bill-gertz It depends of how you install it, but it look ok. In our appliances we install and run xo-server as a global service, and there is only /etc/xo-server/config.toml which is used for user customization (you could remove it and it would still work).
  • akurzawaA

    can we run simple bash sript in cron in xoa?

    5
    0 Votes
    5 Posts
    873 Views
    akurzawaA
    I can put the script everywhere - but I want to avoid non standard config. In case of failure of {system} I'm reinstalling it, and restoring config from file. I don't need to remember that I've put some fancy staff somewhere on the lan.
  • D

    This topic is deleted!

    2
    1
    0 Votes
    2 Posts
    31 Views
  • G

    Restore backup with XO community ed, does not find any destination SRs

    3
    0 Votes
    3 Posts
    1k Views
    G
    @Danp thanks for responding. Your suggestions are very good, caused me to check other things and reveal some things: My metadata and XOA config backups have started to fail with the error 'no such object' The metadata/config backup job's pool parameter was highlighted red with a warning symbol, showing a long GUID style id. I could not update the pool parameter - I have the spinning circle (of doom). After deleting the metadata/config backup job, I cannot recreate it - similar problem with pool parameter, none shown plus spinnng circle (of ongoing doom). To cut a story shorter - I think I have fixed my problem by re-attaching the hosts/SRs to my XOA-community VM... Then I also noticed that the 'successful' backups are not successful as when I looked at their logs by clicking on the green 'successful' indicator in the backup logs I see they are skipping missing VMs. Terrific. So I have now updated all the jobs and reselected each VM, saved them and then re-run the backups. So my big concern (understatement) is my XOA host VM backups have gone bad without any external changes, other than my applying XOA community updates. Do I need to check the backups carefully after every update? Surely not? Perhaps my method of updating, by running a script is horribly HORRIBLY flawed?? I found and have used an update script by Jarli01, applied as noted here. I've got a script to pull the latest update script and execute it. Not clear if I should inbclude the '-b stable' parameter. #!/bin/bash sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash To answer your useful questions: Q. When did you last pull from the source? A. Assume you mean 'when did I last retore from the backup volume'? Never. This is a first time for me. Q. What type of SR(s) should be showing? A. I have two: a local xcp-ng host (also hosting the XOA-community VM being used) and a remote xcp-ng host. Although it does seem an SR is an xcp-ng host, I am confused to the nomclature of 'SR' - I will try to find that out with Google ;). However, as mentioned above my hosts had disconnected themselves... WTF? Q. Are you able to target an SR when defining a new backup job? A. No! OMG. Also noticed the VMs have stopped being shown, no hostts connected!! WTF? Q. Have I opened dev tools (F12), checked console for errors? A. No, but I will when I next report something. Checking the backup page today I do get an error in index.js. I am happy to debug more and return trace/debug data if it is useful; below is what I see today on the backups page: [React Intl] Error formatting time. RangeError: date value is not finite in DateTimeFormat.format() index.js:525 Z index.js:525 formatTime index.js:719 value index.js:1168 React 81 _renderOverlay Portal.js:84 componentDidMount Portal.js:47 m factory.js:665 React 12 notifyAll close closeAll perform perform perform S closeAll perform batchedUpdates batchedUpdates dispatchEvent Q. Check system logs? A. Assume you mean from xoa vm? I will include those next time I post - when I find where they are. Google will no doubt help me out there.
  • S

    Workload Balancing Issue.

    1
    0 Votes
    1 Posts
    340 Views
    No one has replied
  • P

    Build error during upgrade

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    P
    I have isolated the problem. The issue was with dynamic memory allocation on our test server. This was definitely a localized issue. Cheers
  • A

    Feature request - RDP Link in Console window

    4
    1 Votes
    4 Posts
    2k Views
    A
    @olivierlambert https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-uri a plain rpd://ip-address seems to work fine in Mac OS and iOS but more information may be needed on windows clients not sure if the uris work on all systems the same. EDIT Looks like windows doesn't support URI to RDP but Microsoft makes it work for basically every other OS. I still think its a worthwhile feature even if it is slightly less functional because Microsoft is weird.
  • ForzaF

    Zstd instead of zlib?

    5
    0 Votes
    5 Posts
    546 Views
    ForzaF
    Normal backup jobs. In this case it is the "full" copy of the VDI I just moved to a local SR (due to maintenance on the NFS) I mentioned here https://xcp-ng.org/forum/topic/2247/moved-vdi-delta-backup-restarts-on-full. I see that Control Domain load is high and in top I see this: [image: 1574324430375-ea0c91a9-d64d-4403-b97e-e00103b6f7a2-image.png] At the moment it is only one disk left to transfer, but there were 3 to start with, so the load was higher in the beginning.
  • ForzaF

    Moved VDI, delta backup restarts on full

    3
    0 Votes
    3 Posts
    577 Views
    ForzaF
    OH ok. Hope you can prioritize this soon
  • R

    Continuous replication fails every time

    31
    1
    0 Votes
    31 Posts
    13k Views
    olivierlambertO
    Your CR issue might be related to a XO bug on master, not too a XCP-ng issue
  • V

    VDI_IO_ERROR(Device I/O errors) when trying to restore a Delta

    6
    0 Votes
    6 Posts
    2k Views
    V
    Sorry, I was trying to execute the git command in the wrong directory, my bad. Everything worked perfectly, the restores worked now. Thank you very much @Danp.
  • GheppyG

    error on copy VM cross pools

    12
    0 Votes
    12 Posts
    2k Views
    julien-fJ
    I'm working on it at this very moment, I'll let you know what I find.
  • M

    Continuous Replication -> SR Disk space

    2
    0 Votes
    2 Posts
    597 Views
    olivierlambertO
    Hi, There is different things one must consider during CR: SR type: block based or file based? First one will be thick provisioned, so plan a lot of space (eg: local LVM, LVM over iSCSI etc.). Local ext/XFS, NFS or XOSAN aren't affected by this problem Snapshot left: to do a delta, we must have a way to compare to something. The snapshot which left on the SR is the one that will be used for the next backup. It will be compared to the current disk state and only the delta will be sent. So that's perfectly normal "Job canceled to protect the VDI chain": this is a protection to avoid doing another backup while the previous removed snapshot isn't coalesced. You have a link in the message, please refer to the documentation for details
  • R

    Restore of VMs

    15
    0 Votes
    15 Posts
    2k Views
    R
    Sure ... this is worth a try!
  • ForzaF

    Disaster Recovery with Delta

    Solved
    3
    0 Votes
    3 Posts
    529 Views
    ForzaF
    @olivierlambert right. Of course. Forgot about that option