Categories

  • All news regarding Xen and XCP-ng ecosystem

    140 Topics
    4k Posts
    B
    I made a first "demonstrator" preview release for macOS, will upload .deb and .rpm packages as well: https://github.com/benapetr/XenAdminQt/releases/tag/v0.0.1-alpha
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    R
    @andSmv I definitely think it would be nice with support even though i repurposed my M2 Coral for other uses. But one thing to keep in mind regarding resources is that the product would appear to be heading to https://killedbygoogle.com coral.ai redirects to their new NPU offering and no updates have been made from google to the driver since 2022... Mouser still has plenty of stock though. Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either.
  • 3k Topics
    27k Posts
    P
    Hi, latest XOA 6.0.3 I found a case where I can provoke the [image: 1767808902510-8ae00fdb-ab5d-4edc-ba05-95e252a2a5dd-b9996169-f642-4fa6-883b-a1f757e52fb9.png] I do not understand why it happens, but it is happening anyway. We have a normal DELTA backup job with 6 VMs in it. say VM1 to VM6. This job has advanced options of NBD+CBT checked. NBD network exists to do the backup. Normal snapshot mode. Merge Synchronously in advanced is checked. Another job : CONTINUOUS REPLICATION, same 6 VMs, same advanced options checked and a last job : DISASTER RECOVERY of a subset of two VMs : VM4 and VM6 ZSTD compression, normal snapshot mode, merge backup synchronously. 1 point retention (a full is done each time, as intended) All 3 jobs are in sequence, they do not overlap. first backup, second replica, third DR. All 3 jobs execute with success, but in the BACKUP and REPLICA jobs : only VM4 and VM6 have [image: 1767809309153-703c771e-d223-45ac-aff7-6487238be1b0-b9996169-f642-4fa6-883b-a1f757e52fb9.png] with "delta" backup type at the end. the fact that the DR job is done one these two VMs provoke this behavior. this is not wanted. What we see in REPLICA job log : [image: 1767809484517-7d8bdcda-ce93-4541-8513-f83ea28ab46e-929e2473-40bb-4aa3-ab8d-bdcff75b3744.png] And in backup JOB log : [image: 1767809554670-47ce2123-3492-45fd-a61a-6ab5307b68d9-9c9cd199-af57-4b41-9c87-21762c5c2cdb.png] I checked on VM VDI after the DR job is finished and CBT is still checked [image: 1767809603385-29f400f1-dcd2-43cc-b235-9de20f072ed5-fbf26978-1efe-4610-87b7-c06f69c7eea0.png] Why does a DR job resets something that make other two jobs fall back to full on these VDIs ?
  • Our hyperconverged storage solution

    39 Topics
    704 Posts
    snk33S
    Any update from someone ? Not having the ability to enable CBT on XOSTOR is really complicated to make replication / DR scenarios. At least to know if this is work in progress or not. If it's not we'll need to pause our PoC and post-pone production schedule waiting for significant update.
  • 31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related