XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 2
    • Followers 0
    • Topics 5
    • Posts 35
    • Groups 0
    msupportM Offline
    1. Home
    2. msupport
    3. Topics

    Topics

    • msupportM

      Veeam 13.1 Rocky9 Linux Appliance: Potential Data Loss with CBT and Workers with Expired Tokens

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      14
      2 Votes
      14 Posts
      1k Views
      acebmxerA
      Veeam scheduled a remote call with me and pulled more log files. Of coarse when we ran the backup job twice in a row both times al vms were successful. Veeam needs to baby sit our backups :). The call was cut short do to internet going down. I have uploaded the logs and waiting to hear back. Update - Veeam took alot more logs from Veeam and from xcp-ng pool. Their response back - I've got someone else getting similiar results, so I'm providing both of your logs to get some insights. Basically when you see the error, it's because something happened to the bitmap we left behind on the previous run and so next run, we re-read the entire disk. I've not found anything super clear to what's going wrong with the bitmap and why its gone, even from the Xen server logs, so I'm hoping from QA's eyes might see what I might be missing. I will keep you posted if they have any details. Update 8.26.26 - I just wanted to provide an update, the QA team is still checking stuff, but they did advised the following. They noticed for the disks, they show there are configured XO native backups: ie. xo:backup:deltaChainLength: 4; xo:backup:contentKey: 4bce47c7-04bb-44ae-a687-c35c9cfbb2b2; xo:backup:job: e3616a64-6b83-4bd0-80b1-00523678e909; xo:backup:includeNonNbdQcow2Fix: true; xo:backup:schedule: 3488baee-fe48-4acb-a5d0-e728fe28efa1; xo:backup:vm: 5703adef-d804-6b15-ba2f-7b3357a711bb; xo:backup:datetime: 20260819T01:00:33Z I believe you said the native XO Backup was disabled, can you re-confirm if that is accurate, and provide a screenshot for XO's Job and backup list to verify. QA did confirm that native XO Backups can cause issues as it treats the objects as two different chains and so that's why a CBT comparison can fail. QA says they are looking into ways to change how the comparison works in a future update, and expects it to help if in situations if there are native backups, but asked if the Native backup can be verified as disabled for now. I have respnded stating that Veeam backup is only used for Windows based vms. Backup in Xen Orchestra is only used for linux base vms.
    • msupportM

      IPMI Plug-In for HPE DL380 Gen10 ILO5

      Watching Ignoring Scheduled Pinned Locked Moved Management
      3
      1
      0 Votes
      3 Posts
      329 Views
      julienXOvatesJ
      Thanks a lot @msupport ! @all-ki could you add this to our IPMI doc to be published ?
    • msupportM

      XCP-NG Kubernetes micro8k

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      3
      7
      0 Votes
      3 Posts
      1k Views
      nathanael-hN
      Hello @msupport we published a step by step guide, read more in the announcement there https://xcp-ng.org/forum/post/94268
    • msupportM

      Backup VM with active USB Dongle

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      1
      0 Votes
      2 Posts
      463 Views
      ForzaF
      @msupport we use the AnywhereUSB for this reason. Haven't tested the performance with USB disks, but it works good for all our license keys.
    • msupportM

      Vmware migration to XCP-NG no longer works

      Watching Ignoring Scheduled Pinned Locked Moved Solved Xen Orchestra
      18
      0 Votes
      18 Posts
      5k Views
      K
      @olivierlambert Sorry, I will tell it clearly next time.