@Danp I understand, it must be the uuid related to the previous task, but how can I change it and perform the differential copy with the new task?

@Danp In reality, I only found myself in a new backup task with the remote where the complete backup is now and when I execute the task instead of performing the differential copy, I perform the complete backup

Sorry for my English that is translated. The copy is the same, only the other destination storage, the only thing that changes is the task, I cannot use the same one because I have other virtual machines that must stay there.

Hello, I have a delta backup task that I want to move to another storage, I copied all the content to another storage, I made a new copy task and when I execute it it makes a full copy instead of making the differential one, how can I make it continue with the differential copy?

greetings

@DustinB I understand that it does not appear there because the original VM does not exist. The reason could be that when recovering the VM before an emergency the UUID changed and these backups were left behind, I believe that there would be no reason to leave them there if you have new backups of the VM that is being executed or except for some other punctual reason. that your organization needs.

Greetings

@olivierlambert import from xenorchestra web correctly, could it be that it returns that error in cli?

@olivierlambert I didn't try it because I'm far away and the connection is slow, but I'll try it somehow

Good morning, I am trying to import a .ova from xo-upload-ova and I receive

/opt/xen-orchestra/node_modules/.bin/xo-upload-ova --upload /var/xen-orchestra2/vm_test.ova 093a3641-0770-c9c0-b7cd-97c32bc891df --override 'vm_test' descriptionLabel='undefined' memory=json:4294967296 disks.vmdisk1.descriptionLabel='No description' disks.vmdisk1.capacity=json:31457280000 disks.vmdisk2.descriptionLabel='No description' disks.vmdisk2.capacity=json:94371840000
data {
  tables: {
    'vm_test-disk1.vmdk': Promise { <pending> },
    'vm_test-disk2.vmdk': Promise { <pending> }
  },
  disks: {
    vmdisk1: {
      capacity: 31457280000,
      path: 'vm_test-disk1.vmdk',
      compression: undefined,
      descriptionLabel: 'No description',
      nameLabel: 'Hard Disk 1',
      position: 0
    },
    vmdisk2: {
      capacity: 94371840000,
      path: 'vm_test-disk2.vmdk',
      compression: undefined,
      descriptionLabel: 'No description',
      nameLabel: 'Hard Disk 2',
      position: 1
    }
  },
  networks: [ 'ca946202-c104-7c29-6178-bb1f1d69f2c8' ],
  nameLabel: 'vm_test',
  descriptionLabel: undefined,
  nCpus: 2,
  memory: 4294967296
}

ERROR TypeError: _httpRequestPlus.default.post is not a function
    at Object.upload (/opt/xen-orchestra/@xen-orchestra/upload-ova/dist/index.js:225:47)
✖ Cannot read properties of undefined (reading 'readAll')
TypeError: Cannot read properties of undefined (reading 'readAll')
    at Object.upload (/opt/xen-orchestra/@xen-orchestra/upload-ova/dist/index.js:231:55)

@olivierlambert Checking the storage where the delta backups are, I find 13 copies, and I have a retention of 7 configured.

@olivierlambert 6953e

@olivierlambert will this be?

{
  "data": {
    "mode": "delta",
    "reportWhen": "failure"
  },
  "id": "1694649600005",
  "jobId": "b18baa25-8ca5-407c-9b47-3b32919b1c65",
  "jobName": "Backup_hosting2",
  "message": "backup",
  "scheduleId": "6c145708-744f-4a05-a4aa-d7c2fc264ef6",
  "start": 1694649600005,
  "status": "failure",
  "infos": [
    {
      "data": {
        "vms": [
          "62517a8e-8539-d395-c8c2-a2ffb1c7c35e"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "62517a8e-8539-d395-c8c2-a2ffb1c7c35e",
        "name_label": "Hosting2 < (Producción)"
      },
      "id": "1694649608020",
      "message": "backup VM",
      "start": 1694649608020,
      "status": "failure",
      "tasks": [
        {
          "id": "1694649608719",
          "message": "clean-vm",
          "start": 1694649608719,
          "status": "failure",
          "tasks": [
            {
              "id": "1694649609499",
              "message": "merge",
              "start": 1694649609499,
              "status": "failure",
              "end": 1694649618941,
              "result": {
                "generatedMessage": true,
                "code": "ERR_ASSERTION",
                "actual": 295936,
                "expected": 2097664,
                "operator": "strictEqual",
                "message": "Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664",
                "name": "AssertionError",
                "stack": "AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664\n    at VhdFile._read (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdFile.js:124:12)\n    at async VhdFile.mergeBlock (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdAbstract.js:117:19)\n    at async asyncEach.concurrency (/opt/xen-orchestra/packages/vhd-lib/merge.js:208:39)"
              }
            }
          ],
          "end": 1694649618941,
          "result": {
            "generatedMessage": true,
            "code": "ERR_ASSERTION",
            "actual": 295936,
            "expected": 2097664,
            "operator": "strictEqual",
            "message": "Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664",
            "name": "AssertionError",
            "stack": "AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664\n    at VhdFile._read (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdFile.js:124:12)\n    at async VhdFile.mergeBlock (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdAbstract.js:117:19)\n    at async asyncEach.concurrency (/opt/xen-orchestra/packages/vhd-lib/merge.js:208:39)"
          }
        },
        {
          "id": "1694649620779",
          "message": "snapshot",
          "start": 1694649620779,
          "status": "success",
          "end": 1694649622982,
          "result": "f44b9d86-4961-7e71-dbeb-456e93f6058c"
        },
        {
          "data": {
            "id": "082ffdb2-0fee-4e3c-8173-2229b581785d",
            "isFull": false,
            "type": "remote"
          },
          "id": "1694649622983",
          "message": "export",
          "start": 1694649622983,
          "status": "success",
          "tasks": [
            {
              "id": "1694649625892",
              "message": "transfer",
              "start": 1694649625892,
              "status": "success",
              "end": 1694654200433,
              "result": {
                "size": 92109162496
              }
            },
            {
              "id": "1694654201049",
              "message": "clean-vm",
              "start": 1694654201049,
              "status": "success",
              "end": 1694654201977,
              "result": {
                "merge": true
              }
            }
          ],
          "end": 1694654202013
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        }
      ],
      "end": 1694654202014
    }
  ],
  "end": 1694654202014
}

@olivierlambert Yes Oliver, it is the latest version. happened after enabling NBD

Good day, I am using xo-server 5.122.0 and xo-web 5.124.1 compiled from sources and I started getting AssertionError on a Delta backup, however I am seeing the copy in the repository

"id": "1694649608020",
      "message": "backup VM",
      "start": 1694649608020,
      "status": "failure",
      "tasks": [
        {
          "id": "1694649608719",
          "message": "clean-vm",
          "start": 1694649608719,
          "status": "failure",
          "tasks": [
            {
              "id": "1694649609499",
              "message": "merge",
              "start": 1694649609499,
              "status": "failure",
              "end": 1694649618941,
              "result": {
                "generatedMessage": true,
                "code": "ERR_ASSERTION",
                "actual": 295936,
                "expected": 2097664,
                "operator": "strictEqual",
                "message": "Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664",
                "name": "AssertionError",
                "stack": "AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664\n    at VhdFile._read (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdFile.js:124:12)\n    at async VhdFile.mergeBlock (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdAbstract.js:117:19)\n    at async asyncEach.concurrency (/opt/xen-orchestra/packages/vhd-lib/merge.js:208:39)"
              }
            }
          ],
          "end": 1694649618941,
          "result": {
            "generatedMessage": true,
            "code": "ERR_ASSERTION",
            "actual": 295936,
            "expected": 2097664,
            "operator": "strictEqual",
            "message": "Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664",
            "name": "AssertionError",
            "stack": "AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:\n+ actual - expected\n\n+ 295936\n- 2097664\n    at VhdFile._read (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdFile.js:124:12)\n    at async VhdFile.mergeBlock (/opt/xen-orchestra/packages/vhd-lib/Vhd/VhdAbstract.js:117:19)\n    at async asyncEach.concurrency (/opt/xen-orchestra/packages/vhd-lib/merge.js:208:39)"
          }

@exetico tested with virtualbox and it is possible to take a snapshot with VUSB

@exetico I mean when you passthrough a usb, when you want to take a snapshot it gives the error VM_HAS_VUSBS(OpaqueRef:aedd32dc-6dec-4be1-aa5d-9dda799c01b2) and as in version 8.3 you can exclude certain vdi, possibly also a VUSB, that's what I mean

Is it possible to take a snapshot with usb passthrough in version 8.3?

I am playing a bit with SMAPIv3, I created a storage of type file in /mnt/ and a VM, after restarting xcp-ng /mnt/ was not mounted so the storage was not mounted, I did it manually and when starting the VM Throw me

Error code: SR_BACKEND_FAILURE_24
Error parameters: VDIInUse, The VDI is currently in use

I did a detach to the disk from the vm and I also deleted the vm and created a new one but it still gives the same error.

detach and repair does the same

Is there anything new with SMAPIv3?

@olivierlambert thank you

@olivierlambert why should it change if it is a copy of the same delta?