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

    Restoring folder via backup file restore feature broken for .tar.gz

    Scheduled Pinned Locked Moved Backup
    3 Posts 2 Posters 13 Views 2 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.
    • M Online
      MajorP93
      last edited by MajorP93

      Hello XCP-ng community and Vates-Team,

      I just observed a weird behavior of Xen Orchestra during backup file restore.

      Background: I had to restore a directory that got deleted on a small file server Windows VM by accident.

      I used Xen Orchestra's file restore menu to select the VM, restore point and path of the directory in question.
      Initially I selected .tar.gz as export format and started the restore process.
      A new browser tab opened and after a few minutes it showed "Error proxying request".
      Then Xen Orchestra became almost fully unresponsive for like 5min but started to behave normal again after said time.

      I then tried the same thing again: selected same VM, restore point, path etc. but this time opted for ".zip (slow)" option as export format.
      That worked without any issues. Download started after like 5 seconds, no issues whatsoever.

      Did somebody else encounter similar issues?
      Maybe the .tar.gz functionality of Xen Orchestra needs investigation.
      Just wanted to report this issue and ask if maybe somebody else encountered it.

      Thanks and best regards

      //EDIT: oh forgot to mention: I am running a fully patched XCP-ng 8.3 pool and latest XO CE on a Debian 13 VM. NodeJS version is 24 LTS.

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

        @MajorP93 ineresting
        so the same file set to restore was locking the xoa in tar but not in tar gz

        do you know how many files and their size in this folder ?

        M 1 Reply Last reply Reply Quote 1
        • M Online
          MajorP93 @florent
          last edited by MajorP93

          @florent I think you meant it was locking the xoa via .tar.gz but not via .zip which seemed to be the case

          Yeah I just decompressed the restored .zip and checked number of files and size via ncdu, result: "Total disk usage: 194,5 MiB Apparent size: 193,1 MiB Items: 613"

          In case I can provide more information for investigating this issue, please let me know.

          Thanks and best regards

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