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

    A Differential Restore in XO failed and I don't know why. Please help

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 376 Views 1 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.
    • okynnorO Offline
      okynnor
      last edited by

      Hi,

      I was trying to restore one of four available differential backups. When I picked on and the location to restore, I was encountered with the following cryptic error. I hope someone can help me understand and solve this error.

      The error was in the logs under the Message column.

      Much appreciated.

      Values have same structure but are not reference-equal:
      
      Buffer(16) [Uint8Array] [
        11,
        238,
        222,
        110,
        103,
        86,
        77,
        110,
        169,
        135,
        15,
        157,
        26,
        10,
        151,
        26
      

      I should advise that doing a restore straight from the VM was successful. However, when done from the Backup -- Restore --> choose a VM and a differential backup, that fails.

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by Danp

        Is your VM up to date with the latest source (assumes you are running XO and not XOA).

        okynnorO 1 Reply Last reply Reply Quote 0
        • okynnorO Offline
          okynnor @Danp
          last edited by okynnor

          @danp Yes, all my VMs are up-to-date.
          Yes, I am running XO, the free and open sourced version.

          In addition, this happens to all my 11 VMs.

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

            Not your VMs up to date, your XO version. Be sure to be on the latest commit.

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