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

    Detached VM Snapshots after Warm Migration

    Scheduled Pinned Locked Moved Backup
    3 Posts 1 Posters 14 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.
    • DustyArmstrongD Offline
      DustyArmstrong
      last edited by

      I recently migrated all my VMs to new hosts in a new pool via warm migration, which worked great, but I am now seeing "detached snapshots" for the VMs that I moved. I have tested on another VM which was created natively on one of the new hosts and it does not have the same problem.

      It says it has a "Missing VM":

      ff5b9719-c951-4ceb-8b02-048737513911-image.png

      I also recently migrated from a Xen Orchestra container to another (x86 -> ARM), but unsure if that has anything to do with it - I restored my XO config from a metadata backup. The natively created VM was made after this move.

      Is there something I need to do or re-configure to prevent this? The snapshots appear to work, but I have not yet tried to revert to one.

      DustyArmstrongD 1 Reply Last reply Reply Quote 0
      • DustyArmstrongD Offline
        DustyArmstrong @DustyArmstrong
        last edited by DustyArmstrong

        Looked at some other posts, it seems it probably does have something to do with my old XO. This is no longer active, can I re-associate the VMs with my current XO instance? I imported my config from a backup, so I thought that would cover it, my new XO instance spun up exactly like the old one.

        Broken snapshot (logs show it initiated from the pool master's IP):

        5505 HTTPS 123.456.789.2->:::80|Async.VM.snapshot

        ALLOWED' 'OK' 'API' 'VM.snapshot' (('vm' '' '' 'OpaqueRef:cce8c856-3310-a551-7cf3-f3ec6d68903d')

        Working snapshot (logs show it initiated from my XO's IP):

        62327 HTTPS 123.456.789.6->|Async.VM.snapshot

        ALLOWED' 'OK' 'API' 'VM.snapshot' (('vm' 'CCTV' 'cd95df02-a907-bdaa-2c0e-ca503656460b' 'OpaqueRef:00c31a47-69d9-753d-5481-d5a10e881e13')

        So it seems that the broken VMs are being initiated from the host they run on, not XO.

        DustyArmstrongD 1 Reply Last reply Reply Quote 0
        • DustyArmstrongD Offline
          DustyArmstrong @DustyArmstrong
          last edited by

          OK, I still had my old pool master registered as a server in XO (disabled), removing this and restarting XO now shows the VMs properly in the audit logs when snapshot, and it shows them being initiated by my XO IP, but the snapshots are still seen as detached ("Missing VM").

          Maybe it will just resolve itself eventually if XAPI is holding onto stale references? I still have my old backups ("Detached backups") that I'm waiting to remove (job itself removed), maybe that's also impacting things - I will be removing the backed up VHDs once my NAS has copied them to an external drive (very slow!).

          I'm not opposed to blowing XO away and starting it over, I need to start a new backup job anyway - if there's a procedure/best practice to go by in order to re-create all the metadata I'd be interested.

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