XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XO Community edition backups dont work as of build 6b263

    Scheduled Pinned Locked Moved Backup
    60 Posts 16 Posters 1.3k Views 14 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      katapaltes @florent
      last edited by

      Hello @florent , the results below between 8:04:10 and 8:04:36 seem to align with one of the three failed VM backups. NB: The error did not return when I did another Delta backup (everything backed up successfully). I am now doing a Force Full Backup on all VMs just to be safe. As of now I am still running 1a7b5 and have not yet updated to 7994f.

      Jun 23 08:01:14 sxoap31 xo-server[19663]: }
Jun 23 08:04:10 sxoap31 xo-server[19663]: 2025-06-23T13:04:10.703Z xo:backups:MixinBackupWriter WARN cleanVm: incorrect backup size in metadata {
Jun 23 08:04:10 sxoap31 xo-server[19663]:   path: '/xo-vm-backups/bca06bdf-3e1f-40a4-570e-7b584b356e22/20250623T130122Z.json',
Jun 23 08:04:10 sxoap31 xo-server[19663]:   actual: 12283019264,
Jun 23 08:04:10 sxoap31 xo-server[19663]:   expected: 12288363520
Jun 23 08:04:10 sxoap31 xo-server[19663]: }
Jun 23 08:04:31 sxoap31 xo-server[19663]: 2025-06-23T13:04:31.411Z @xen-orchestra/xapi/disks/Xapi WARN openNbdCBT XapiError: SR_BACKEND_FAILURE_460(, Failed to calculate changed blocks for given VDIs. [opterr=Source and target V>
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/_XapiError.mjs:16:12)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at default (file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/_getTaskResult.mjs:13:29)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/index.mjs:1073:24)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/index.mjs:1107:14
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at Array.forEach (<anonymous>)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/index.mjs:1097:12)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202506230729/packages/xen-api/index.mjs:1270:14)
Jun 23 08:04:31 sxoap31 xo-server[19663]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
Jun 23 08:04:31 sxoap31 xo-server[19663]:   code: 'SR_BACKEND_FAILURE_460',
Jun 23 08:04:31 sxoap31 xo-server[19663]:   params: [
Jun 23 08:04:31 sxoap31 xo-server[19663]:     '',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     ''
Jun 23 08:04:31 sxoap31 xo-server[19663]:   ],
Jun 23 08:04:31 sxoap31 xo-server[19663]:   call: undefined,
Jun 23 08:04:31 sxoap31 xo-server[19663]:   url: undefined,
Jun 23 08:04:31 sxoap31 xo-server[19663]:   task: task {
Jun 23 08:04:31 sxoap31 xo-server[19663]:     uuid: 'aeac5fce-c3c8-d3d5-eff0-f1aa3b7dc4dc',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     name_label: 'Async.VDI.list_changed_blocks',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     name_description: '',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     allowed_operations: [],
Jun 23 08:04:31 sxoap31 xo-server[19663]:     current_operations: {},
Jun 23 08:04:31 sxoap31 xo-server[19663]:     created: '20250623T13:04:30Z',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     finished: '20250623T13:04:30Z',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     status: 'failure',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     resident_on: 'OpaqueRef:e9735ec6-f9a5-da8a-0891-262ae26db402',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     progress: 1,
Jun 23 08:04:31 sxoap31 xo-server[19663]:     type: '<none/>',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     result: '',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     error_info: [
Jun 23 08:04:31 sxoap31 xo-server[19663]:       'SR_BACKEND_FAILURE_460',
Jun 23 08:04:31 sxoap31 xo-server[19663]:       '',
Jun 23 08:04:31 sxoap31 xo-server[19663]:       'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]',
Jun 23 08:04:31 sxoap31 xo-server[19663]:       ''
Jun 23 08:04:31 sxoap31 xo-server[19663]:     ],
Jun 23 08:04:31 sxoap31 xo-server[19663]:     other_config: {},
Jun 23 08:04:31 sxoap31 xo-server[19663]:     subtask_of: 'OpaqueRef:NULL',
Jun 23 08:04:31 sxoap31 xo-server[19663]:     subtasks: [],
Jun 23 08:04:31 sxoap31 xo-server[19663]:     backtrace: '(((process xapi)(filename lib/backtrace.ml)(line 210))((process xapi)(filename ocaml/xapi/storage_utils.ml)(line 141))((process xapi)(filename ocaml/xapi/message_forwardi>
Jun 23 08:04:31 sxoap31 xo-server[19663]:   }
Jun 23 08:04:31 sxoap31 xo-server[19663]: }
Jun 23 08:04:36 sxoap31 xo-server[19663]: 2025-06-23T13:04:36.914Z xo:xapi:vdi WARN invalid HTTP header in response body {
Jun 23 08:04:36 sxoap31 xo-server[19663]:   body: 'HTTP/1.1 500 Internal Error\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     'content-length: 318\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     'content-type: text/html\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     'connection: close\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     'cache-control: no-cache, no-store\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     '\r\n' +
Jun 23 08:04:36 sxoap31 xo-server[19663]:     '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representati>
Jun 23 08:04:36 sxoap31 xo-server[19663]: }
Jun 23 08:05:14 sxoap31 systemd-timesyncd[412]: Timed out waiting for reply from 23.155.40.38:123 (0.debian.pool.ntp.org).
      1 Reply Last reply Reply Quote 0
      • A Offline
        archw
        last edited by

        All is well for me ...thanks for the hard work!

        1 Reply Last reply Reply Quote 0
        • marcoiM Offline
          marcoi
          last edited by

          Seems like backup are broken again for me. I tried the latest build.
          Xen Orchestra, commit d8370

          Im seeing two kinds of errors:
          Error 1 The job starts and does nothing. I do see it creating a snap shot as I deleted the existing snapshot as part of testing

          Error2: The job runs and fails with http error.

          Testing so far:
          XO config backup still work fine.

          f6d51b31-0b35-4e5d-a234-7d8dc4700b72-image.png

          a1ed0564-6e9c-46e2-872b-3636ce5c3616-image.png

          marcoiM 1 Reply Last reply Reply Quote 0
          • marcoiM Offline
            marcoi @marcoi
            last edited by 

            {
  "data": {
    "mode": "delta",
    "reportWhen": "failure"
  },
  "id": "1750967273856",
  "jobId": "79a021e6-9637-40f0-871f-ab122f104d65",
  "jobName": "2D. Dev VM - 6AM - Full: Sunday - Daily:M-F",
  "message": "backup",
  "scheduleId": "60635a8f-6aa9-4988-96eb-376faaabf740",
  "start": 1750967273856,
  "status": "pending",
  "infos": [
    {
      "data": {
        "vms": [
          "4b999d5b-6bbf-78b5-93f2-83747c879be6",
          "1c29eb9f-5b4b-2a63-dee2-47b738701058"
        ]
      },
      "message": "vms"
    }

            So I deleted the backup snap shot of one of the two VMs in this backup job. I then did full backup and the job shows running but stuck in pending mode. I do see two folders on my NAS with the same vms ids, which are empty. So its just not doing the backup process.

            c8654207-3c33-4dbd-81c9-95132346da78-image.png

            marcoiM florentF 2 Replies Last reply Reply Quote 0
            • marcoiM Offline
              marcoi @marcoi
              last edited by

              rollbacked to Xen Orchestra, commit bda87 and same issue. Trying to see if i can go further back.

              1 Reply Last reply Reply Quote 0
              • D Offline
                DustinB @Danp
                last edited by

                @Danp said in XO Community edition backups dont work as of build 6b263:

                @wf said in XO Community edition backups dont work as of build 6b263:

                How do I roll back to a previous commit?

                git checkout <target commit>

                Then rebuild with yarn; yarn build

                @marcoi use the above to roll back to a specific commit.

                1 Reply Last reply Reply Quote 0
                • florentF Offline
                  florent Vates 🪐 XO Team @marcoi
                  last edited by

                  @marcoi
                  is there any error message in XO logs ? (like journalctl )

                  marcoiM 1 Reply Last reply Reply Quote 0
                  • marcoiM Offline
                    marcoi @florent
                    last edited by

                    @florent
                    are you asking about logs available in the gui or are there any logs stored locally under XO install for example?

                    1 Reply Last reply Reply Quote 0
                    • marcoiM Offline
                      marcoi
                      last edited by marcoi

                      Here are the tasks that show up when i try running a full backup.
                      a64ee111-7acb-412d-a89a-11af0f9c77f8-image.png

                      Seems it does not do anything after the snap shot.
                      Im current running Xen Orchestra, commit 1cb9c
                      Will update to the latest commit and see what it does.

                      here part of the log of backup while it sitting in Started. you see tasks are sitting in pending.

                             {
          "data": {
            "id": "f992fff1-e245-48f7-8eb3-25987ecbfbd4",
            "isFull": true,
            "type": "remote"
          },
          "id": "1751028165392:0",
          "message": "export",
          "start": 1751028165392,
          "status": "pending",
          "tasks": [
            {
              "id": "1751028165994",
              "message": "transfer",
              "start": 1751028165994,
              "status": "pending"
            }

                      Update 2 ( i updated to latest Xen Orchestra, commit 54141)
                      I deleted the snaps of prior backup attempts from each VM and ran a full backup job again.
                      You can see it did the snap tasks (create/cleanup) but it still pending on export and transfer.

                           "id": "1751028772562",
      "message": "backup VM",
      "start": 1751028772562,
      "status": "pending",
      "tasks": [
        {
          "id": "1751028772569",
          "message": "clean-vm",
          "start": 1751028772569,
          "status": "success",
          "end": 1751028772628,
          "result": {
            "merge": false
          }
        },
        {
          "id": "1751028772999",
          "message": "snapshot",
          "start": 1751028772999,
          "status": "success",
          "end": 1751028778291,
          "result": "db1a49fb-10af-026d-7d27-4ff0f5da97c6"
        },
        {
          "data": {
            "id": "f992fff1-e245-48f7-8eb3-25987ecbfbd4",
            "isFull": true,
            "type": "remote"
          },
          "id": "1751028778291:0",
          "message": "export",
          "start": 1751028778291,
          "status": "pending",
          "tasks": [
            {
              "id": "1751028778863",
              "message": "transfer",
              "start": 1751028778863,
              "status": "pending"
                      marcoiM 1 Reply Last reply Reply Quote 0
                      • marcoiM Offline
                        marcoi @marcoi
                        last edited by

                        I got this from the syslog file. some error are showing up when i ran backup job.

                        2025-06-27T09:40:56.178745-04:00 xen xo-server[2283]: (node:2283) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
2025-06-27T09:40:56.178843-04:00 xen xo-server[2283]: (Use `node --trace-deprecation ...` to show where the warning was created)
2025-06-27T09:40:56.182409-04:00 xen xo-server[2283]: 2025-06-27T13:40:56.178Z xo:xo-server WARN Node warning {
2025-06-27T09:40:56.182468-04:00 xen xo-server[2283]:   error: DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
2025-06-27T09:40:56.182496-04:00 xen xo-server[2283]:       at IncomingMessage.flash (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/connect-flash/lib/flash.js:67:16)
2025-06-27T09:40:56.182526-04:00 xen xo-server[2283]:       at file:///opt/xo/xo-builds/xen-orchestra-202506270848/packages/xo-server/src/index.mjs:322:11
2025-06-27T09:40:56.182552-04:00 xen xo-server[2283]:       at Layer.handle [as handle_request] (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/layer.js:95:5)
2025-06-27T09:40:56.182580-04:00 xen xo-server[2283]:       at trim_prefix (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:328:13)
2025-06-27T09:40:56.182603-04:00 xen xo-server[2283]:       at /opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:286:9
2025-06-27T09:40:56.182633-04:00 xen xo-server[2283]:       at Function.process_params (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:346:12)
2025-06-27T09:40:56.182656-04:00 xen xo-server[2283]:       at next (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:280:10)
2025-06-27T09:40:56.182679-04:00 xen xo-server[2283]:       at Xo._handleHttpRequest (file:///opt/xo/xo-builds/xen-orchestra-202506270848/packages/xo-server/src/xo.mjs:173:7)
2025-06-27T09:40:56.182704-04:00 xen xo-server[2283]:       at Layer.handle [as handle_request] (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/layer.js:95:5)
2025-06-27T09:40:56.182744-04:00 xen xo-server[2283]:       at trim_prefix (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:328:13)
2025-06-27T09:40:56.182767-04:00 xen xo-server[2283]:       at /opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:286:9
2025-06-27T09:40:56.182822-04:00 xen xo-server[2283]:       at Function.process_params (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:346:12)
2025-06-27T09:40:56.182845-04:00 xen xo-server[2283]:       at next (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:280:10)
2025-06-27T09:40:56.182883-04:00 xen xo-server[2283]:       at initialize (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/passport/lib/middleware/initialize.js:98:5)
2025-06-27T09:40:56.182907-04:00 xen xo-server[2283]:       at Layer.handle [as handle_request] (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/layer.js:95:5)
2025-06-27T09:40:56.182945-04:00 xen xo-server[2283]:       at trim_prefix (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:328:13)
2025-06-27T09:40:56.182970-04:00 xen xo-server[2283]:       at /opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:286:9
2025-06-27T09:40:56.182994-04:00 xen xo-server[2283]:       at Function.process_params (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:346:12)
2025-06-27T09:40:56.183018-04:00 xen xo-server[2283]:       at next (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:280:10)
2025-06-27T09:40:56.183041-04:00 xen xo-server[2283]:       at urlencodedParser (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/body-parser/lib/types/urlencoded.js:94:7)
2025-06-27T09:40:56.183072-04:00 xen xo-server[2283]:       at Layer.handle [as handle_request] (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/layer.js:95:5)
2025-06-27T09:40:56.183105-04:00 xen xo-server[2283]:       at trim_prefix (/opt/xo/xo-builds/xen-orchestra-202506270848/node_modules/express/lib/router/index.js:328:13) {
2025-06-27T09:40:56.183136-04:00 xen xo-server[2283]:     code: 'DEP0044'
2025-06-27T09:40:56.183166-04:00 xen xo-server[2283]:   }
2025-06-27T09:40:56.183212-04:00 xen xo-server[2283]: }
2025-06-27T09:41:16.131076-04:00 xen xo-server[2352]: 2025-06-27T13:41:16.129Z xo:backups:worker INFO starting backup
2025-06-27T09:41:16.842684-04:00 xen xo-server[2352]: 2025-06-27T13:41:16.842Z xo:backups:MixinBackupWriter INFO deleting temporary VHD {
2025-06-27T09:41:16.842762-04:00 xen xo-server[2352]:   path: '/xo-vm-backups/4b999d5b-6bbf-78b5-93f2-83747c879be6/vdis/79a021e6-9637-40f0-871f-ab122f104d65/9aa754da-084f-4cc3-a494-2de58e17387c/.20250627T130633Z.vhd'
2025-06-27T09:41:16.842806-04:00 xen xo-server[2352]: }
2025-06-27T09:41:16.843337-04:00 xen xo-server[2352]: 2025-06-27T13:41:16.843Z xo:backups:MixinBackupWriter INFO deleting temporary VHD {
2025-06-27T09:41:16.843372-04:00 xen xo-server[2352]:   path: '/xo-vm-backups/1c29eb9f-5b4b-2a63-dee2-47b738701058/vdis/79a021e6-9637-40f0-871f-ab122f104d65/a48c797e-39b2-4d9a-84a1-d4323436430f/.20250627T130627Z.vhd'
2025-06-27T09:41:16.843415-04:00 xen xo-server[2352]: }
2025-06-27T09:41:16.847122-04:00 xen xo-server[2352]: 2025-06-27T13:41:16.846Z xo:backups:MixinBackupWriter INFO deleting unused VHD {
2025-06-27T09:41:16.847160-04:00 xen xo-server[2352]:   path: '/xo-vm-backups/4b999d5b-6bbf-78b5-93f2-83747c879be6/vdis/79a021e6-9637-40f0-871f-ab122f104d65/9aa754da-084f-4cc3-a494-2de58e17387c/.20250627T130633Z.vhd'
2025-06-27T09:41:16.847178-04:00 xen xo-server[2352]: }
2025-06-27T09:41:16.847260-04:00 xen xo-server[2352]: 2025-06-27T13:41:16.847Z xo:backups:MixinBackupWriter INFO deleting unused VHD {
2025-06-27T09:41:16.847311-04:00 xen xo-server[2352]:   path: '/xo-vm-backups/1c29eb9f-5b4b-2a63-dee2-47b738701058/vdis/79a021e6-9637-40f0-871f-ab122f104d65/a48c797e-39b2-4d9a-84a1-d4323436430f/.20250627T130627Z.vhd'
2025-06-27T09:41:16.847334-04:00 xen xo-server[2352]: }
2025-06-27T09:41:18.829536-04:00 xen xo-server[2352]: 2025-06-27T13:41:18.828Z xo:backups:worker WARN possibly unhandled rejection {
2025-06-27T09:41:18.829591-04:00 xen xo-server[2352]:   error: TypeError: this.source.readBlock is not a function
2025-06-27T09:41:18.829612-04:00 xen xo-server[2352]:       at XapiDiskSource.readBlock (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:70:28)
2025-06-27T09:41:18.829627-04:00 xen xo-server[2352]:       at XapiDiskSource.buildDiskBlockGenerator (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/Disk.mjs:69:28)
2025-06-27T09:41:18.829642-04:00 xen xo-server[2352]:       at buildDiskBlockGenerator.next (<anonymous>)
2025-06-27T09:41:18.829658-04:00 xen xo-server[2352]:       at XapiDiskSource.diskBlocks (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/Disk.mjs:27:39)
2025-06-27T09:41:18.829673-04:00 xen xo-server[2352]:       at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-06-27T09:41:18.829687-04:00 xen xo-server[2352]:       at async Promise.all (index 0)
2025-06-27T09:41:18.829705-04:00 xen xo-server[2352]: }
2025-06-27T09:41:27.192451-04:00 xen xo-server[2352]: 2025-06-27T13:41:27.192Z xo:backups:worker WARN possibly unhandled rejection {
2025-06-27T09:41:27.192549-04:00 xen xo-server[2352]:   error: TypeError: this.source.readBlock is not a function
2025-06-27T09:41:27.192576-04:00 xen xo-server[2352]:       at XapiDiskSource.readBlock (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:70:28)
2025-06-27T09:41:27.192606-04:00 xen xo-server[2352]:       at XapiDiskSource.buildDiskBlockGenerator (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/Disk.mjs:69:28)
2025-06-27T09:41:27.192627-04:00 xen xo-server[2352]:       at buildDiskBlockGenerator.next (<anonymous>)
2025-06-27T09:41:27.192657-04:00 xen xo-server[2352]:       at XapiDiskSource.diskBlocks (file:///opt/xo/xo-builds/xen-orchestra-202506270848/@xen-orchestra/disk-transform/dist/Disk.mjs:27:39)
2025-06-27T09:41:27.192686-04:00 xen xo-server[2352]:       at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-06-27T09:41:27.192715-04:00 xen xo-server[2352]:       at async Promise.all (index 0)
2025-06-27T09:41:27.192750-04:00 xen xo-server[2352]: }
                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          archw
                          last edited by

                          I'm on build d8370 and last night all my backups ran without issue.

                          1 Reply Last reply Reply Quote 0
                          • itservicesI Offline
                            itservices
                            last edited by itservices

                            Hi.

                            I am on commit 2effd and have the same problem.

                            Snapshots are being created but no transfer is taking place.

                            Regards,
                            Marc

                            marcoiM 1 Reply Last reply Reply Quote 0
                            • marcoiM Offline
                              marcoi @itservices
                              last edited by

                              @itservices
                              also the same with Xen Orchestra, commit 2effd

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Offline
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by

                                Check with fcefaae

                                R 1 Reply Last reply Reply Quote 0
                                • marcoiM Offline
                                  marcoi
                                  last edited by

                                  looks like Xen Orchestra, commit fcefa might have fixed the backup issue. I am running a backup test now and it showing export step running
                                  61668884-b733-4650-961d-1d171e83e2ce-image.png

                                  1 Reply Last reply Reply Quote 0
                                  • R Offline
                                    RobWhalley @olivierlambert
                                    last edited by

                                    @olivierlambert Sadly, it's not working for me - I've updated to the latest commit and tested a job that should take around 5 minutes; it's been stuck on "Started" for a couple of hours now.

                                    marcoiM 1 Reply Last reply Reply Quote 0
                                    • marcoiM Offline
                                      marcoi @RobWhalley
                                      last edited by

                                      @RobWhalley did you try to restart the service or reboot the server running XO? I have a nightly crontab job that updates the OS, updates XO and then reboots the server.

                                      R 1 Reply Last reply Reply Quote 0
                                      • R Offline
                                        RobWhalley @marcoi
                                        last edited by

                                        @marcoi Hi, the service restarted as part of the upgrade process, but I have done a restart of the VM running Orchestra as well, just to be on the safe side.

                                        Please see attached log.txt for additional log information.

                                        git log shows the expected commit:

                                        /opt/xo/xo-builds/xen-orchestra-202506301106# git log
commit fcefaaea85651c3c0bb40bfba8199dd4e963211c (HEAD, origin/master, origin/HEAD)
Author: Pierre Brunet <pierre.demonthelie@gmail.com>
Date:   Mon Jun 30 10:43:41 2025 +0200

    feat: technical release (#8767)
                                        marcoiM 1 Reply Last reply Reply Quote 0
                                        • olivierlambertO Offline
                                          olivierlambert Vates 🪐 Co-Founder CEO
                                          last edited by

                                          The rebuild maybe?

                                          1 Reply Last reply Reply Quote 0
                                          • marcoiM Offline
                                            marcoi @RobWhalley
                                            last edited by

                                            @RobWhalley to see if it's behaving the same as what I saw on prior versions can you do the following steps?

                                            1. open tasks in a new browser window so you can monitor it. If you can keep the backup window and task window side by side you can see if the export command comes and goes quickly.
                                              1.a If you go between backup and tasks in the same window, ive noticed the prior task history clears out.

                                            2. ssh into the VM running XO and monitor the syslog
                                              tail -100f /var/log/syslog
                                              #may need root then try sudo tail -100f /var/log/syslog

                                            3. In primary window kick off a backup then watch the task window to see if export command comes and goes.
                                              c7563916-882b-4077-87eb-7591b871b057-image.png

                                            4. If the task disappears then click on previous tasks and see if you even had export command come up.

                                            5. reply with the results of how task shows export step and any errors in the syslog file.

                                            Hopefully that helps the devs figure out whats going on in your system.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post