Backup: ERR_OUT_OF_RANGE in RemoteVhdDisk.mergeBlock

[olivierlambert]

Question for @florent I assume

[florent]

@olivierlambert I am summoning @simonp that worked on the merge last month ( in fact he is already working on it)

[florent]

did you resize the VM disks in the near past ?

[simonp]

Hi @wralb, thank you for the report.

We have identified the source of the issue and implemented a potential fix. It's currently on the branch fix_merge_out_of_range.

Could you check it out, retry the backup and confirm that the issue issue is fixed ?

Thanks.

[wralb]

@florent, yes, the VM has a single disk and I did enlarge it by a few GB in the last couple of weeks.

[wralb]

@simonp Thanks! Will have a go as soon as I can.

[wralb]

Hi @simonp, thanks again. Great service!!

I have checked out your fix branch and re-run the backup. It succeeded as seen here:

{
  "data": {
    "mode": "delta",
    "reportWhen": "always"
  },
  "id": "1772725052650",
  "jobId": "73d72ea9-f25e-4c88-878c-98af27c1a827",
  "jobName": "Daily backup of Unix VMs with changing data",
  "message": "backup",
  "scheduleId": "9cbc3238-382d-4fae-83c0-4e92348898e5",
  "start": 1772725052650,
  "status": "success",
  "infos": [
    {
      "data": {
        "vms": [
          "c54a256e-0493-5c6d-a0cd-c3a4618f99a1"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "c54a256e-0493-5c6d-a0cd-c3a4618f99a1",
        "name_label": "MailCW"
      },
      "id": "1772725054418",
      "message": "backup VM",
      "start": 1772725054418,
      "status": "success",
      "tasks": [
        {
          "id": "1772725054426",
          "message": "clean-vm",
          "start": 1772725054426,
          "status": "success",
          "tasks": [
            {
              "id": "1772725055044",
              "message": "merge",
              "start": 1772725055044,
              "status": "success",
              "end": 1772725196294
            }
          ],
          "end": 1772725196304,
          "result": {
            "merge": true
          }
        },
        {
          "id": "1772725197030",
          "message": "snapshot",
          "start": 1772725197030,
          "status": "success",
          "end": 1772725198708,
          "result": "e46c757e-9180-2502-81c5-36a2fb2928fc"
        },
        {
          "data": {
            "id": "fd6bbd08-52dd-43eb-84df-f93b54fc28e9",
            "isFull": false,
            "type": "remote"
          },
          "id": "1772725198708:0",
          "message": "export",
          "start": 1772725198708,
          "status": "success",
          "tasks": [
            {
              "id": "1772725200147",
              "message": "transfer",
              "start": 1772725200147,
              "status": "success",
              "end": 1772725224785,
              "result": {
                "size": 2768240640
              }
            },
            {
              "id": "1772725225673",
              "message": "clean-vm",
              "start": 1772725225673,
              "status": "success",
              "end": 1772725225747,
              "result": {
                "merge": true
              }
            }
          ],
          "end": 1772725225757
        }
      ],
      "end": 1772725225758
    }
  ],
  "end": 1772725225759
}

[simonp]

@wralb Perfect, thanks for getting back to us.

So the issue only occurs when a delta backup tries to backup a disk that has had an increase in size, so you can either stay on the branch or go back to master if you are not planning on enlarging any disks in the near future.

Anyways, the fix should be available in the next patch or release.

Thanks.

[wralb]

@simonp Thanks for the extra information; very helpful. I will revert to master as I don't routinely enlarge disks.

[florent]

@wralb this will impact each merges with different sizes, so if you revert to master you may still have the issue

this commit will probably be in master by monday

[wralb]

@florent Understood. Thanks.

[florent]

@wralb it is in master, we are preparing a patch release for XOA on monday morning with this fix