<?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/ -->
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:lj="https://www.livejournal.com">
  <id>urn:lj:livejournal.com:atom1:openvz</id>
  <title>OpenVZ</title>
  <subtitle>OpenVZ</subtitle>
  <author>
    <name>OpenVZ</name>
  </author>
  <link rel="alternate" type="text/html" href="https://openvz.livejournal.com/"/>
  <link rel="self" type="text/xml" href="https://openvz.livejournal.com/data/atom"/>
  <updated>2015-08-06T15:41:27Z</updated>
  <lj:journal userid="9392309" username="openvz" type="community"/>
  <link rel="service.feed" type="application/x.atom+xml" href="https://openvz.livejournal.com/data/atom" title="OpenVZ"/>
  <entry>
    <id>urn:lj:livejournal.com:atom1:openvz:52010</id>
    <author>
      <name>Сергей Бронников</name>
    </author>
    <lj:poster user="estetus" userid="12957684"/>
    <link rel="alternate" type="text/html" href="https://openvz.livejournal.com/52010.html"/>
    <link rel="self" type="text/xml" href="https://openvz.livejournal.com/data/atom/?itemid=52010"/>
    <title>OpenVZ upgrade and migration script</title>
    <published>2015-08-06T15:40:33Z</published>
    <updated>2015-08-06T15:41:27Z</updated>
    <category term="openvz"/>
    <category term="upgrade"/>
    <content type="html">&lt;i&gt;Author:&lt;/i&gt; Andre Moruga&lt;br /&gt;&lt;br /&gt;Every now and then our team is asked question "How do I move a container created on OpenVZ to Virtuozzo"? This is one of the issues which will be finally resolved in version 7 that we are now working on  (&lt;a href="https://openvz.org/Virtuozzo_7_Technical_Preview_-_Containers" target="_blank" rel="nofollow"&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="https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse/ovztransfer.sh" target="_blank" rel="nofollow"&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 "not template based" - which means tools for template management (like adding an application via vzpkg) won'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'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="mailto:users@openvz.org" target="_blank" rel="nofollow"&gt;users@openvz.org&lt;/a&gt;.</content>
  </entry>
</feed>
