<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. https://www.livejournal.com/bots/  -->
<rss version='2.0'  xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>OpenVZ</title>
  <link>https://openvz.livejournal.com/</link>
  <description>OpenVZ - LiveJournal.com</description>
  <lastBuildDate>Thu, 06 Aug 2015 15:40:33 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>openvz</lj:journal>
  <lj:journalid>9392309</lj:journalid>
  <lj:journaltype>community</lj:journaltype>
  <image>
    <url>https://l-userpic.livejournal.com/128680075/9392309</url>
    <title>OpenVZ</title>
    <link>https://openvz.livejournal.com/</link>
    <width>100</width>
    <height>100</height>
  </image>

  <item>
  <guid isPermaLink='true'>https://openvz.livejournal.com/52010.html</guid>
  <pubDate>Thu, 06 Aug 2015 15:40:33 GMT</pubDate>
  <title>OpenVZ upgrade and migration script</title>
  <author>estetus</author>
  <link>https://openvz.livejournal.com/52010.html</link>
  <description>&lt;i&gt;Author:&lt;/i&gt; Andre Moruga&lt;br /&gt;&lt;br /&gt;Every now and then our team is asked question &quot;How do I move a container created on OpenVZ to Virtuozzo&quot;? This is one of the issues which will be finally resolved in version 7 that we are now working on  (&lt;a href=&quot;https://openvz.org/Virtuozzo_7_Technical_Preview_-_Containers&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;first technical preview&lt;/a&gt; is just out). In this version the compatibility will be on binary and transfer protocol levels. So the regular mechanisms (like container migration) will work out of the box.&lt;br /&gt;In prior version this task, although not technically difficult, is not very straightforward, the data images cannot be simply moved - depending on configuration used in OpenVZ, they may be incompatible.Besides, an OpenVZ based container will have configuration that needs to be updated to fit the new platform.&lt;br /&gt;To facilitate such migrations, we created a script which automates all these operations: data transfer, migrating container configuration, and tuning configuration to ensure container will work on the new platform.&lt;br /&gt;The script is available at &lt;a href=&quot;https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse/ovztransfer.sh&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse/ovztransfer.sh&lt;/a&gt;. Its usage is simple: run it in the source (old) node, and specify destination host IP and list of containers to be migrated:&lt;br /&gt;&lt;br /&gt;&lt;pre&gt;
 $ ./ovztransfer.sh TARGET_HOST SOURCE_VEID0:[TARGET_VEID0] ...
&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;For example:&lt;br /&gt;&lt;br /&gt;&lt;pre&gt;
 ./ovztransfer.sh 10.1.1.3 101 102 103
&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;The script has been designed to migrate containers from older OpenVZ versions to v.7; however it should also work migrating data to existing Virtuozzo versions (like 6.0).&lt;br /&gt;There is one restriction: containers based on obsolete templates that do not exist on the destination servers will be transferred as &quot;not template based&quot; - which means tools for template management (like adding an application via vzpkg) won&apos;t work for them.&lt;br /&gt;This is a first version of this script; we will have an opportunity to improve it before the final release. That&apos;s why your feedback (or even code contributions) is important here.&lt;br /&gt;If you tried it and want to share your thoughts, email to OpenVZ user group at &lt;a href=&quot;mailto:users@openvz.org&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;users@openvz.org&lt;/a&gt;.</description>
  <comments>https://openvz.livejournal.com/52010.html?view=comments#comments</comments>
  <category>openvz</category>
  <category>upgrade</category>
  <lj:security>public</lj:security>
  <lj:poster>estetus</lj:poster>
  <lj:posterid>12957684</lj:posterid>
  <lj:reply-count>2</lj:reply-count>
  </item>
</channel>
</rss>
