This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
virtualization:xenserver:xenserver_migration [2017/01/28 13:51] gcooper |
virtualization:xenserver:xenserver_migration [2017/04/12 13:56] (current) gcooper |
||
---|---|---|---|
Line 24: | Line 24: | ||
See also **[[computing: | See also **[[computing: | ||
- | :!: In the following commands, it is **required to configure SSH keys** prior. | + | https:// |
- | ==== Transfer Two VMs from One Pool to Another ==== | + | :!: In the following commands, it is **necessary |
- | https://techblog.jeppson.org/ | + | Using these commands, VMs are transferred (actually, exported and imported) directly from one ' |
+ | |||
+ | 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. | :!: VMs must be **shut down** before transferring with these commands. | ||
- | CLI example: | + | :!: Add '' |
+ | |||
+ | CLI example, as '' | ||
+ | |||
+ | < | ||
+ | xe vm-export uuid=< | ||
+ | </ | ||
+ | |||
+ | ==== Transfer Two VMs from One Pool to Another ==== | ||
< | < | ||
Line 39: | Line 53: | ||
==== Transfer a Template and a VM from One Pool to Another ==== | ==== Transfer a Template and a VM from One Pool to Another ==== | ||
- | |||
- | CLI example: | ||
< | < | ||
xe template-export template-uuid=< | xe template-export template-uuid=< | ||
+ | </ | ||
+ | |||
+ | ===== Export/ | ||
+ | |||
+ | < | ||
+ | xe vm-export vm=" | ||
+ | |||
+ | xe vm-import filename="/ | ||
</ | </ |