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

    Created VM from Fast Clone, Now How to Separate

    Scheduled Pinned Locked Moved Xen Orchestra
    5 Posts 2 Posters 34 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.
    • H Offline
      hawkpro
      last edited by

      Due to a time crunch, created a VM from an existing VM's snapshot, using the fast clone option. This new VM is now running the way we want and I would like to get away from its reliance on the original VM's snapshot.

      What is the best path forward in a circumstance like this?

      Thanks

      bvitnikB 1 Reply Last reply Reply Quote 0
      • bvitnikB Offline
        bvitnik @hawkpro
        last edited by

        @hawkpro If you have multiple SRs, move the VM to some other SR.

        H 1 Reply Last reply Reply Quote 0
        • H Offline
          hawkpro
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • H Offline
            hawkpro @bvitnik
            last edited by

            @bvitnik

            I can do that, though, at this time, we're using 2 XCP hosts with local storage. The last test I did for migrating an entire VM, went well and had some unexpected downtime as ARP (I believe) caught up.

            Would a continuous replication job do the trick? This way the downtime could be better controlled.

            Thanks

            bvitnikB 1 Reply Last reply Reply Quote 0
            • bvitnikB Offline
              bvitnik @hawkpro
              last edited by

              @hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence.

              Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR.

              If you have extended downtimes of your VM migrations, then something is not quite right with your setup.

              1 Reply Last reply Reply Quote 0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              • First post
                Last post