1. Home
  2. Xen Orchestra

Subcategories

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

    365 Topics
    3k Posts
    B
    @Danp THANKS! That did the trick. I was able to clean up after doing that. Thanks so much!

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

    90 Topics
    766 Posts
    D
    @Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!

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

    374 Topics
    4k Posts
    burbilogB
    I have a delta backup job with Full backup interval set to 7. If i look at the backup job results I get this: xoce (legion) Snapshot Start: 2025-07-25 03:02 End: 2025-07-25 03:02 Fiend NFS transfer Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Size: 23.78 GiB Speed: 73.01 MiB/s Clean VM directory cleanVm: incorrect backup size in metadata Start: 2025-07-25 03:08 End: 2025-07-25 03:08 Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Type: full It says "full". If i go to backup -> restore, search for this vm, i see "full 2 delta 2" in "Available Backups" column. Yet if i press "restore" arrow i see that two full backups are of 2022 year and it looks dangerous. Documentation says about that setting "For example, with a value of 2, the first two backups will be a key and a delta, and the third will start a new chain with a full backup.". Yet, I see only VERY old full backups... Xen Orchestra, commit 19412 Master, commit 6277a, but it seems that this happens for a long time (i recently updated it to this state and the problem seems to persist ever since I began to use Xen Orchestra in 2022). Do I miss something? Do I really have fresh full backups and these a just labeled "incremental" or what? [image: 1753444452743-xoce.png]

  • Everything related to Xen Orchestra's REST API

    66 Topics
    502 Posts
    lsouai-vatesL
    @StephenAOINS This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints. We are currently finalizing the migration of existing endpoints, the next step will be adding new ones. We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts. have a good day

  • Terraform, Packer or any tool to do IaC

    34 Topics
    319 Posts
    olivierlambertO
    No, it's fine, as long the issue contains all the relevant details it's fine
Log in to post
Load new posts
  • N

    NFS ISO: Cannot read property 'Export' of undefined

    Solved
    8
    0 Votes
    8 Posts
    1k Views
    N
    @olivierlambert said in NFS ISO: Cannot read property 'Export' of undefined: Let's consider this thread fixed by adding the correct NFS configuration on the server side and create a new one describing your issue.
  • N

    Manually Mount A HD When Needed From XCP-ng?

    docking station mount hd
    3
    0 Votes
    3 Posts
    323 Views
    N
    @ravenet said in Manually Mount A HD When Needed From XCP-ng?: You can script mount and umount commands as part of jobs or as part of backup jobs.
  • V

    balance-alb on XOA

    4
    0 Votes
    4 Posts
    296 Views
    olivierlambertO
    Yes
  • mauzillaM

    Risks of running a shared pool?

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    You can't add a host into another pool until it's "blank". It's hard to "merge" two pools together. So first, migrate VMs to the destination, clean the host and THEN add it to the pool.
  • V

    Technical requirements for XOA for backup.

    6
    0 Votes
    6 Posts
    701 Views
    olivierlambertO
    No need to update XCP-ng, we don't want to introduce a dedicated agent. It will rely on another mechanism. We'll publish about it before the end of this summer
  • abravionA

    XOA incorrect size in metadata

    3
    1
    1 Votes
    3 Posts
    418 Views
    gcooperG
    First off, thank you very much Vates for this fantastic project. I appreciate it greatly. This is happening to us too after the last (CE) update. Buggin' me bad... G
  • J

    XO 5.72 Storage Maintenance

    6
    0 Votes
    6 Posts
    1k Views
    J
    @geoffbland Hi, thanks for the reply... That's what I wound up doing, installing XO from source on a Raspberry PI that I had. I used it to restore my XO image from backup, once I did that I had to restore all of my guests (12 of them total). I could never figure out how to get my SR out of maintenance mode, so I wound up creating a new SR and restored each backup to the new SR. All back to normal after restoring the backup. Thank god XO backup works so well! I learned the hard way that I need to move my XO disks to local storage before I enter maintenance mode for my iSCSI SR... Oh well, lesson learned!
  • S

    Delta backup schedule randomly performing full backups

    4
    3
    0 Votes
    4 Posts
    302 Views
    S
    Hi @olivierlambert we have just come across the same issue again today after the latest update. Please see below the log file for the delta backup schedule that performed full backups instead. I can't seem to find anything in the logs to help. 2022-07-12T16_00_00.013Z-backupNG.txt
  • D

    XOA multiple networks

    5
    0 Votes
    5 Posts
    1k Views
    D
    @olivierlambert ahh perfect thanks!
  • peterbaumertP

    Netbox Plugin Enhancements

    8
    0 Votes
    8 Posts
    1k Views
    peterbaumertP
    @pdonias said in Netbox Plugin Enhancements: Why do you have those interfaces? Could you explain your use case and why they're not visible in XO? Sorry, you're right, hosts are not synced for a simple reason: there is no such thing as host types in Netbox (or did we miss something?). So we only group VMs by pools (clusters) and that's it. Those interfaces are for example wireguard interfaces or any other virtual interfaces. Obv they are not in xo because they are virtual, but in netbox they are needed because I deploy all my wireguard stuff with them. The host thing already was answered, there are devices which you then can link to Pools. KR Peter
  • A

    Opening the BIOS in a vmguest

    9
    0 Votes
    9 Posts
    4k Views
    A
    @olivierlambert Thank you for sharing that information, that is an additional knowledge for me.
  • A

    XO from source Centos7 GLIBC_2.25 missing error

    11
    0 Votes
    11 Posts
    2k Views
    A
    @olivierlambert Thanks. My other instance is on Ubuntu. It updated without problems. But it seems new version have problems with session timeout. Now It logging out few times a day)
  • GriAleG

    invalid credentials in new installation from source

    9
    0 Votes
    9 Posts
    1k Views
    julien-fJ
    @GriAle Should be fixed: https://github.com/vatesfr/xen-orchestra/commit/ba03a4849831deecda7b8139374b5c43bf90d2b3 0 julien-f committed to vatesfr/xen-orchestra chore(xo-server): update to hashy@0.11.1 Fixes https://xcp-ng.org/forum/post/50866 Introduced by 49890a09b7a3c4bcbe7f462577c6d0a7da8b7006 Fixes argon2id support which is the new default algorithm since argon2@0.28.7
  • Spunky_SurveyorS

    XVA might be broken on Delta Backup

    4
    1
    0 Votes
    4 Posts
    683 Views
    Spunky_SurveyorS
    @julien-f It is likely a broken xva. I did interrupt those as they were exporting, however I was a bit confused as to why it was checked by a different backup task. In other words this screen clip is from a delta backup, not a xva export. I was more expecting it to show up on the XVA export backup task.
  • A

    Backup automatic retry

    7
    0 Votes
    7 Posts
    471 Views
    A
    @florent @olivierlambert Looking at failed S3 backup problems the retry should be easy. Currently on the job report there is a button to restart all failed VM backups in that job. Can you just add an option for automatic restart failed VM backups after job completion. It can even be a separate job (just as clicking the button is). It would just "click" the restart failed VMs button once (or a setting) after a few minutes (or a setting). Or it could start the new job as pending or delayed and start after a few minutes allowing for time to cancel it.
  • A

    Not seeing tasks any more (as admin)

    11
    0 Votes
    11 Posts
    1k Views
    T
    Thank you, that fix worked.
  • northportioN

    XO fails to backup 1 specific VM due to: Error: HTTP connection has timed out

    backup backups-reports delta
    14
    3
    1 Votes
    14 Posts
    2k Views
    M
    @olivierlambert i have created config.httpInactivityTimeout.toml in /opt/xen-orchestra/packages/xo-server with the content from above. Not sure how i can check if thats actually set. BTW: this is not a CR Backup Problem, i also dont see Tasks running for my "normal" Backup Job. I cant check "how far" the actual Backup runs and if that differs. https://github.com/vatesfr/xen-orchestra/pull/6315 Rajaa-BARHTAOUI opened this pull request in vatesfr/xen-orchestra closed fix(xo-web/tasks): tasks with no bound objects not displayed #6315
  • E

    how do i migrate VM storage to a different SR

    3
    0 Votes
    3 Posts
    2k Views
    E
    @olivierlambert thanks
  • GheppyG

    tasks not sowing in XOCE

    8
    0 Votes
    8 Posts
    649 Views
    rajaa-bR
    Hello, we will take a look into that and keep you posted.
  • Z

    Backup a VM with all its snapshots?

    14
    0 Votes
    14 Posts
    4k Views
    G
    @Zevgeny For a few snapshots it's fine - the issue comes when you have large numbers. Most of my first-hand experience with this specific issue comes from Hyper-V but the logic applies here. This is from VMware but the concept is the same and has some good reading on snapshots in general. Running a virtual machine on a snapshot for extended periods of time can cause instability and data loss. https://kb.vmware.com/s/article/1015180 The underlying issue stems from the nature of snapshots. With none you have a single VHD containing all of the data for the VM, once you take a snapshot a new delta VHD is created with all new data written going forward from the time of the snapshot. So, in order to have a complete VM you have the original VHD + the delta VHD. This is fine in smaller numbers, but once you start having 10, 15, 20+ snapshots, every one of those represents an additional VHD in the chain. This results in performance degradation because you're reading from multiple potential files as only new data is written to the deltas. This is actually from XO's blog: https://xen-orchestra.com/blog/xenserver-coalesce-detection-in-xen-orchestra/