<div dir="ltr">Not going to argue with that, it&#39;s rather pointless, but:<div><a href="http://www.ovirt.org/OVirt_3.5_Release_Notes#Import_Storage_Domain">http://www.ovirt.org/OVirt_3.5_Release_Notes#Import_Storage_Domain</a><br></div><div><br></div><div>Now this feature only needs to make it into RHEV.</div><div><br></div><div>My suggestion is as safe as it gets, in fact I migrated a large setup from 2.2 to 3.4 this summer with no problems</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 20, 2014 at 3:42 PM, John Gardeniers <span dir="ltr">&lt;<a href="mailto:jgardeniers@objectmastery.com" target="_blank">jgardeniers@objectmastery.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Thanks Dan,<br>
    <br>
    If that&#39;s the case it would be an extremely time-consuming and
    painful process, even to the point where it may not even be viable.
    <span><span> :-( </span></span><br>
    <br>
    It&#39;s increasingly looking to me like a deliberate decision has been
    taken to make it as difficult as possible to migrate VMs away from
    Ovirt/RHEV. It&#39;s the only virtualisation system I&#39;ve encountered
    that doesn&#39;t have a real export system (export domains don&#39;t cut
    it).<br>
    <br>
    regards,<br>
    John<div><div class="h5"><br>
    <br>
    <br>
    <div>On 21/11/14 07:27, Dan Yasny wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Not an official answer here, but I&#39;d assume the
        procedure would be to redeploy the engine and hosts, and use
        export domains</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Nov 20, 2014 at 3:21 PM, John
          Gardeniers <span dir="ltr">&lt;<a href="mailto:jgardeniers@objectmastery.com" target="_blank">jgardeniers@objectmastery.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Bump.<br>
            <br>
            On 17/11/14 15:41, John Gardeniers wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              What is the procedure to use when migrating Ovirt to or
              from RHEV? I&#39;m assuming of course that there&#39;s little
              difference for the two directions. Is it just a matter of
              detaching the storage domain(s), dumping the engine
              database and attaching/importing them into the other
              system?<br>
              <br>
              regards,<br>
              John<br>
              <br>
              _______________________________________________<br>
              Users mailing list<br>
              <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
              <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
              <br>
              ______________________________________________________________________<br>
              This email has been scanned by the Symantec Email
              Security.cloud service.<br>
              For more information please visit <a href="http://www.symanteccloud.com" target="_blank">http://www.symanteccloud.com</a><br>
              ______________________________________________________________________<br>
            </blockquote>
            <br>
            _______________________________________________<br>
            Users mailing list<br>
            <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
            <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br clear="all">
______________________________________________________________________<br>
      This email has been scanned by the Symantec Email Security.cloud
      service.<br>
      For more information please visit <a href="http://www.symanteccloud.com" target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div>