• Need FeedBack: New version of the File level restore

    Pinned
    12
    2 Votes
    12 Posts
    1k Views
    florentF
    the new code is now in master
  • CBT: the thread to centralize your feedback

    Pinned
    456
    1 Votes
    456 Posts
    863k Views
    G
    Hello, Just a feedback. I am having trouble using CBT Backups with NBD. Host Details: XCP-NG Version : 8.3 latest (stable) Xen Orchestra: latest:stable (From Source) The first full backup always seems to work. The delta backup gives the error: 'HANDLE_INVALID' the writer IncrementalXapiWriter has failed the step writer.checkBaseVdis() with error HANDLE_INVALID(VBD, OpaqueRef:xxxxx). It won't be used anymore in this job execution. Start: 2026-08-09 14:01 End: 2026-08-09 14:01 Duration: a few seconds Error: HANDLE_INVALID(VBD, OpaqueRef:xxxxxx) This is a XenServer/XCP-ng error
  • Feedback on immutability

    Pinned
    58
    2 Votes
    58 Posts
    30k Views
    P
    @gsszuber Hi, Yes indeed, you need to preserve the root of the bucket from Lifecycle. We just had a customer with a similar issue. Can you help us by giving a small screenshot of the field to filter out the root (or filter in the three folders) please?
  • Why are transfer sizes different between XO5 & XO6?

    Solved
    16
    2
    0 Votes
    16 Posts
    291 Views
    P
    @JorisK said: fix/update-transfer-size-calculation Confirming that the branch fixes it
  • 2 Votes
    17 Posts
    2k Views
    acebmxerA
    Just recieved another update from veeam... Regarding the general earlier errors: Warning : Failed to use CBT: [Task e75c4247-2ee1-7b51-088c-b970ace60f3d (Async.VDI.list_changed_blocks) failed: . SR_BACKEND_FAILURE_460. . Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated] Our QA team did hear back from Vates support, who says its tied to a recent bug they've found with blktap calls: https://github.com/xapi-project/blktap/pull/444 Our QA engineer hasn't heard back yet on ETA when it will be pushed out in a general release yet though
  • How to fixture out what is using backup storage?

    Unsolved
    3
    0 Votes
    3 Posts
    122 Views
    A
    @poddingue Thank you!!!
  • XOA 6.8 Pool Metadata backup

    7
    0 Votes
    7 Posts
    408 Views
    F
    @poddingue This was fixed a number of weeks ago via a ticket. I believe @florent may know the exact fix.
  • Can't init vhd directory without using alias

    Unsolved
    2
    0 Votes
    2 Posts
    120 Views
    poddingueP
    You already spotted this over on 12468, so this is just to close the loop here. That one's fixed: Pierre Brunet put the fix on a branch, @Andrew and @abudef both tested it, and it's merged now. Since you're running from source on master, you should be able to pull past that merge rather than wait for a release. One thing to keep in mind, though: the same error string showed up in 11875 for a completely different cause, so if it comes back after you update, it's probably not this bug again. I'd let 12468 be the thread to follow since that's where the people who fixed it are.
  • Error: Can't init vhd directory without using alias

    Solved
    12
    1 Votes
    12 Posts
    613 Views
    A
    @pierrebrunet Tested and working again, thanks
  • Master, commit a3139 failing backups

    Solved
    23
    0 Votes
    23 Posts
    3k Views
    P
    @jr-m4 Hi, We have found this issue in another thread, it is now merged
  • 0 Votes
    114 Posts
    19k Views
    poddingueP
    Thanks a lot for your feeback, folks!
  • Backup remote repository structure

    2
    0 Votes
    2 Posts
    152 Views
    P
    @abudef Hi, Do you think this doc can help you? Link to doc I think it needs some improvements, feel free to enhance it if you feel it is necessary!
  • 0 Votes
    20 Posts
    1k Views
    P
    @florent No explicit assigned migration or backup network set. Backups generate errors somewhat randomly. As one VM won't get the "error" one time. But on the next backup run it will. And the third time it might not. This even happens on VMs that are turned off, and therefore shouldn't have any changed bytes between backups. Host is reachable from XO Network has NBD enabled All VMs use VHD IPv4 Backup type is Delta
  • XOA 6.8 causes backup / replication failure

    Unsolved
    18
    1
    0 Votes
    18 Posts
    822 Views
    florentF
    @acebmxer we are far more explicit on the real usage of NBD, paing the way to mark a failed NBD connexion as an error in a few month also working on a diagnostic tool to be more efficient on the checks thank you all for your time
  • 0 Votes
    5 Posts
    312 Views
    P
    @poddingue said: I haven't used that tab myself, and since it's built around VMs that do have backups, I don't know if it gives you the negative view you want. If it doesn't, https://feedback.vates.tech is where that gets counted. Maybe you can build some sort of filter but I don't think so. I'll use https://feedback.vates.tech for future suggestions. Tks
  • Error mirroring full backups to backblaze b2

    Solved
    33
    2
    0 Votes
    33 Posts
    5k Views
    poddingueP
    Thanks a lot for this feedback, @pedro!
  • Full backups: Why is it not possible to use NBD on full backups ?

    Solved
    3
    0 Votes
    3 Posts
    269 Views
    P
    That should be it, tks @poddingue
  • Title: Slow Backup Performance with Commvault Agentless Backup on XCP-ng Cluster

    Unsolved
    10
    0 Votes
    10 Posts
    3k Views
    R
    Anyone who is using Commvault to back up VMs please tell me what you are using for credintials since you have to connect directly to a pool? I am looking for a way to backup VMs using Commvault and us AD accounts or OIDC.
  • Backup failures with odd connection refused errors

    Unsolved
    7
    0 Votes
    7 Posts
    521 Views
    poddingueP
    Thanks for the feedback.
  • Backup status reporting failure when retry was successful

    7
    2
    1 Votes
    7 Posts
    709 Views
    poddingueP
    XO 6.7.0 went out on 30 July, and the changelog carries Bastien's fix under Backups as "Fix failed status on successful retry", pointing at PR https://github.com/vatesfr/xen-orchestra/pull/10129 and back at this thread: https://xen-orchestra.com/blog/xen-orchestra-6-7/. Given what you said about keeping the backup XOA on a version you trust, I would not rush it, but that is the version to look for when you do move. I have not exercised the retry path myself, so if a retried VM still reports the job as failed after you upgrade, it is worth saying so here.