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

    Failed vm restore

    Scheduled Pinned Locked Moved Backup
    11 Posts 2 Posters 58 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.
    • F Offline
      frank-s
      last edited by

      Hopefully the times when restore is needed is hardly ever or even never. This morning, however, following a major power outage that took out an entire street, on reboot one of the vms was damaged and wouldn't boot. This vm has 2 vdis but each vdi is on a different SR. I attempted a differential restore specifying the correct SR for each vdi but the restore failed to start. It failed with the error: "Choose a SR and a Backup". I had chosen a backup from 18:00Hrs last night and I selected "For each VDI, select an SR" specifying the correct SR for each of the two vdis.
      Because it did not work, and I was under pressure, I chose instead to create a new vm from the snapshot associated the same backup. It created the new vm instantly (fast clone) and it booted OK. So the client is happy, but I am left wondering if future restores will be reliable. Was my procedure correct? Can anyone throw any light on this for me? XCP-NG 8.2.1 is fully patched and XO (from the sources) is relatively recent but not completely up to date. Xen Orchestra, commit 6ecab Master, commit d499f.
      Thanks.

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

        Hi,

        I don't see anything wrong in the way you described the restore. Outside that, as you use the version from the sources, there's no stability guarantee.

        But at least, you must (especially after having an issue) update to the latest possible commit on master. Otherwise, it's impossible to assist even in here. There's 16k+ commits in Xen Orchestra, and each one can yield a different problem or fix 😄

        Check the logs for more info, but first, as repeated many times and written in big yellow warning in the doc, please update to latest commit on master.

        F 1 Reply Last reply Reply Quote 0
        • F Offline
          frank-s @olivierlambert
          last edited by

          @olivierlambert Thanks Olivier. I will update XO and retry the restore. I'll let you know the outcome.

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

            Thanks, keep us posted!

            F 1 Reply Last reply Reply Quote 0
            • F Offline
              frank-s @olivierlambert
              last edited by

              @olivierlambert I have updated XO Xen Orchestra, commit fe92e Master, commit d8370. I tried to restore a small vm with only one vdi. I can confirm that this error still happens but only if I use "For each VDI, select an SR". Otherwise it restores OK but, of course, any additional vdis would be restored to the same SR. I still wonder if I'm doing something wrong. Here is a screenshot of my restore dialog:

              5192d170-9030-4a33-b744-6b2089e828ec-image.png

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

                Can you please uncheck "Use differential restore" to see if it changes the outcome?

                That would be interesting to get the logs of the failed restore too, maybe it's a trivial UI bug on restore when it's done on 2 different SRs 🤔

                F 1 Reply Last reply Reply Quote 0
                • F Offline
                  frank-s @olivierlambert
                  last edited by

                  @olivierlambert I have not done this with the vm I needed to restore this morning. It's very large and I don't want a massive daya copy during working hours. I tried what you asked with a small vm and I did not turn on differential restore. I got the same error. Nothing appears to be logged for the time the error happened.

                  53c445fb-87b2-4a95-8580-92a147c6cd3c-image.png

                  F 1 Reply Last reply Reply Quote 0
                  • F Offline
                    frank-s @frank-s
                    last edited by

                    Please note that if I don't use "For each VDI, select an SR" the backup restores normally. This is true whether or not differential restore is turned on.

                    22d945c8-c03d-42cc-bebf-49ff5d9781a9-image.png

                    F 1 Reply Last reply Reply Quote 0
                    • F Offline
                      frank-s @frank-s
                      last edited by

                      FYI: I have tried this on a completely different installation with a different client - same error, but without "For each VDI, select an SR" restore is OK
                      Thanks.

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

                        Thanks, so it's an XO bug. Pinging @lsouai-vates

                        F 1 Reply Last reply Reply Quote 0
                        • F Offline
                          frank-s @olivierlambert
                          last edited by

                          @olivierlambert Thanks. I'll watch for the outcome. Appreciate all that you guys do.

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