Previous page

Next page

Locate page in Contents

Print this page

migrate_v2v

Summary:

Migrates a Virtuozzo Container from one Hardware Node to another.

Request specification:

Name

Min/Max

Type

Description

migrate_v2v

1..1

 

 

{

 

 

 

options

0..1

v2v_migrate_optionsType

Migration options.

eid

1..1

eid_type

Server ID of the source Container.

dst

1..1

connection_infoType

The destination Hardware Node connection information.

You must specify the name, realm, and password parameters that are valid on the destination Hardware Node. If, for example, you are authenticating the user on the target node against a certain Realm but don't know the Realm ID in advance, you must connect to the destination node first and get the Realm ID using the get_realm call. Alternately, you may use the generate_pass call to get a temporary login info and use the returned values to populate this structure. The generate_pass call must also be executed on the target Hardware Node.

}

 

 

 

Returns:

OK/Error

Description:

To migrate a Virtuozzo Container, the target host must have Virtuozzo Containers and Parallels Agent software installed.

The following V2V migration types are supported:

On successful migration, the original Container will no longer exist on the source node. This is done in order to avoid possible conflicts that may occur if both the original and the new Containers are running at the same time. However, the original Container data will NOT be deleted from the source Hardware Node. By default, the data is kept in its original location (the Container private area) but the private area directory itself will be renamed. You can completely remove the original Container data from the source node by including the options/remove parameter in the request.

Linux Example:

Performing an offline migration (type 0). The progress argument is set to "on" to receive the migration progress messages.

Input

<packet version="4.0.0" progress="on">

<target>relocator</target>

<data>

<relocator>

<migrate_v2v>

<options>

<force/>

<nostart/>

<type>0</type>

</options>

<eid>a8a73d01-2969-6b48-9544-5cbf6ea7c554</eid>

<dst>

<protocol>SSL</protocol>

<address>192.168.0.240</address>

<login>

<name>cm9vdA==</name>

<realm>00000000-0000-0000-0000-000000000000</realm>

</login>

<password>bXlwYXNz</password>

<port>4434</port>

</dst>

</migrate_v2v>

</relocator>

</data>

</packet>

Output

The following is an example of a progress message received during the migration process:

<?xml version="1.0" encoding="UTF-8"?><ns1:packet xmlns:ns1="http://www.swsoft.com/webservices/vzl/4.0.0/protocol" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="4fc46559f47tbdbrd64" time="2007-05-22T02:02:58+0000" type="1" priority="4000" version="4.0.0">

<ns1:origin>relocator</ns1:origin>

<ns1:target>vzclient7-1df4b04e-0d55-f246-b718-89bbc62fd371</ns1:target>

<ns1:dst>

<ns1:director>gend</ns1:director>

</ns1:dst>

<ns1:data>

<ns1:progress>

<ns1:message>

<ns1:message>Q2FsbGluZyB2em1zcmMuLi4=</ns1:message>

<ns1:name></ns1:name>

<ns1:translate/>

<ns1:parameter>

<ns1:message>JXRpdGxlJQ==</ns1:message>

<ns1:name>source_env</ns1:name>

<ns1:translate/>

<ns1:parameter>

<ns1:message>MWRmNGIwNGUtMGQ1NS1mMjQ2LWI3MTgtODliYmM2MmZkMzcx</ns1:message>

<ns1:name>eid</ns1:name>

<ns1:translate/>

</ns1:parameter>

<ns1:parameter>

<ns1:message>ZGhjcDAtMTM2LnN3LnJ1</ns1:message>

<ns1:name>title</ns1:name>

<ns1:translate/>

</ns1:parameter>

<ns1:parameter>

<ns1:message>Z2VuZXJpYw==</ns1:message>

<ns1:name>type</ns1:name>

<ns1:translate/>

</ns1:parameter>

</ns1:parameter>

</ns1:message>

<ns1:status>2</ns1:status>

</ns1:progress>

</ns1:data>

<ns1:src>

<ns1:director>gend</ns1:director>

</ns1:src>

</ns1:packet>

On successful migration, you will receive the standard Agent "OK" message.

<?xml version="1.0" encoding="UTF-8"?><ns1:packet xmlns:ns1="http://www.swsoft.com/webservices/vzl/4.0.0/protocol" xmlns:ns2="http://www.swsoft.com/webservices/vzl/4.0.0/relocator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="4fc46559f47tbdbrd64" time="2007-05-22T02:03:25+0000" priority="4000" version="4.0.0">

<ns1:origin>relocator</ns1:origin>

<ns1:target>vzclient7-1df4b04e-0d55-f246-b718-89bbc62fd371</ns1:target>

<ns1:dst>

<ns1:director>gend</ns1:director>

</ns1:dst>

<ns1:data>

<ns2:relocator>

<ns1:ok/>

</ns2:relocator>

</ns1:data>

<ns1:src>

<ns1:director>gend</ns1:director>

</ns1:src>

</ns1:packet>

Please send us your feedback on this help page