User Tools

Site Tools


virtualization:xenserver:xenserver_migration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
virtualization:xenserver:xenserver_migration [2017/01/28 13:45]
gcooper
virtualization:xenserver:xenserver_migration [2017/04/12 13:56] (current)
gcooper
Line 1: Line 1:
-====== XenServer Migration ======+====== XenServer Migration Issues ======
  
 http://searchservervirtualization.techtarget.com/tip/How-to-configure-Citrix-XenServer-live-migration http://searchservervirtualization.techtarget.com/tip/How-to-configure-Citrix-XenServer-live-migration
Line 20: Line 20:
 http://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/storage-xenmotion-live-storage-migration-with-citrix-xenserver.pdf http://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/storage-xenmotion-live-storage-migration-with-citrix-xenserver.pdf
  
 +===== Migration to a New Pool =====
  
 +See also **[[computing:linux:ssh_keys|Set Up SSH Keys]]**
 +
 +https://techblog.jeppson.org/2016/06/quickly-transfer-vms-xenserver-pools/
 +
 +:!: In the following commands, it is **necessary to configure SSH keys** for password-less access (one direction) prior.
 +
 +Using these commands, VMs are transferred (actually, exported and imported) directly from one 'source pool' member, over a secure SSH connection using the Management network, to a 'destination pool' member.
 +
 +This process will **monopolize Management network bandwidth** for a good long while, affecting/affected by all other Management network traffic for the duration of the transfers.
 +
 +Exporting, then importing will **flatten (coalesce) all VHD chains** in the process...a wonderful thing.
 +
 +==== Transfer a VM from One Pool to Another ====
 +
 +:!: VMs must be **shut down** before transferring with these commands.
 +
 +:!: Add ''sr-uuid=<desired-sr-uuid>'' to ''vm-import'' to specify the **destination SR**.  Alternately, just set the desired destination SR as the pool Default SR using XenCenter.
 +
 +CLI example, as ''root'' at the 'sender' console:
 +
 +<file>
 +xe vm-export uuid=<vm-uuid> filename= | ssh root@<ip-of-new-server> xe vm-import filename=/dev/stdin
 +</file>
 +
 +==== Transfer Two VMs from One Pool to Another ====
 +
 +<file>
 +xe vm-export uuid=<vm-uuid> filename= | ssh root@<ip-of-new-server> xe vm-import filename=/dev/stdin && xe vm-export uuid=<vm-uuid> filename= | ssh root@<ip-of-new-server> xe vm-import filename=/dev/stdin
 +</file>
 +
 +==== Transfer a Template and a VM from One Pool to Another ====
 +
 +<file>
 +xe template-export template-uuid=<template-uuid> filename= | ssh root@<ip-of-new-server> xe vm-import filename=/dev/stdin && xe vm-export uuid=<vm-uuid> filename= | ssh root@<ip-of-new-server> xe vm-import filename=/dev/stdin
 +</file>
 +
 +===== Export/Import to/from Mounted Storage =====
 +
 +<file>
 +xe vm-export vm="Name of VM" filename="/mount/point/Name Of VM.xva"
 +
 +xe vm-import filename="/mount/point/Name Of VM.ova" sr-uuid=<UUID of storage repository to place import> host-username=root host-password=>password of xenserver>
 +</file>
virtualization/xenserver/xenserver_migration.1485636328.txt.gz · Last modified: 2017/01/28 13:45 by gcooper