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

    VM Disk Not Migrating due to Backup Running

    Scheduled Pinned Locked Moved Management
    10 Posts 4 Posters 43 Views 3 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.
    • A Online
      allySalami
      last edited by

      I'm trying to migrate a disk to a different sr, but XOA is stating I can't because a backup is in progress, however, a backup is in fact not in progress. It initially said this when the backup failed, so I re-ran the backup and it successfully completed but the XOA is still telling me it can't migrate due to the backup running. The backup has been finished for days now and it is still giving this message. I also disabled the daily backup schedule to stop the backup from starting again.

      I have tried restarting the toolstack, i have tried rather than using the XOA Community GUI I've used XCPNG-Center but it gives the same message, I've tried to clear any ghost tasks by ssh'ing into the xcpng server and checking for tasks but none of them are showing a backup running. I've tried the following two commands:

      systemctl restart redis-server
      systemctl restart xo-server

      They have not worked. I considered using xe vm-reset-powerstate uuid=<VM_UUID> --force, but my concern is that the VM will stop or restart which is something I do not want to do at this moment.

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

        Question for @florent

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

          Check the VM's Advanced tab to see if this option is enabled --
          f2f9d99e-1648-4d6d-94b5-43d8d6922334-image.png

          A 1 Reply Last reply Reply Quote 0
          • A Online
            allySalami @Danp
            last edited by

            @Danp I don't have that option in the Advanced Tab.

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

              @allySalami I'm not sure how that could be. You checked the VM's Advanced tab, correct? Are you running XOA or XO from sources? What is your current version / commit?

              A 1 Reply Last reply Reply Quote 0
              • A Online
                allySalami @Danp
                last edited by

                @Danp I'm using version 8.3

                A 1 Reply Last reply Reply Quote 0
                • A Offline
                  acebmxer @allySalami
                  last edited by

                  @allySalami

                  click on About in XO...

                  Screenshot_20260220_151640.png

                  Screenshot_20260220_151658.png

                  A 1 Reply Last reply Reply Quote 0
                  • A Online
                    allySalami @acebmxer
                    last edited by

                    @acebmxer!!xoa.JPG

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      acebmxer @allySalami
                      last edited by

                      @allySalami

                      Let someone else comfirm but think you are way out of date on xo. Might be best to deploy a new one.

                      A 1 Reply Last reply Reply Quote 0
                      • A Online
                        allySalami @acebmxer
                        last edited by

                        @acebmxer Yeah, I definitely believe this is not the latest version, but I was told it was kept like that for a reason. Can't quite remember what the reasoning is, as this is for another company who utilizes xoa.

                        But, would running this command ' xe vm-reset-powerstate uuid=<VM_UUID> --force ' reboot the vm?

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