47 lines
2.8 KiB
Markdown
47 lines
2.8 KiB
Markdown
How to move data volume between two VMs using OpenStack Horizon on 3Engines Cloud[🔗](#how-to-move-data-volume-between-two-vms-using-openstack-horizon-on-brand-name "Permalink to this headline")
|
|
===================================================================================================================================================================================================
|
|
|
|
Volumes are used to store data and those data can be accessed from a virtual machine to which the volume is attached. To access data stored on a volume from another virtual machine, you need to disconnect that volume from virtual machine to which it is currently connected, and connect it to another instance.
|
|
|
|
This article uses the Horizon dashboard to transfer volumes between virtual machines which are in the same project.
|
|
|
|
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
|
-------------------------------------------------------------
|
|
|
|
No. 1 **Hosting**
|
|
|
|
You need a 3Engines Cloud hosting account with Horizon interface <https://horizon.3Engines.com>.
|
|
|
|
No. 2 **Source virtual machine and volume**
|
|
|
|
We assume that you have a virtual machine (which we will call *source* virtual machine) to which a volume is attached.
|
|
|
|
No. 3 **Destination virtual machine**
|
|
|
|
We also assume that you want to access the data stored on volume mentioned in Prerequisite No. 2 from another instance which is in the same project - we will call that instance *destination* virtual machine.
|
|
|
|
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
|
---------------------------------------------------------------------------------------
|
|
|
|
> * Ensure that the transfer is possible
|
|
>
|
|
> + Projects must be on the same cloud
|
|
> + Volume cannot be used for booting an operating system
|
|
> + File system compatibility
|
|
> + Making sure that the source virtual machine does not try to access the volume
|
|
> + Other volume and instance conditions for successful transfer
|
|
> * Shutting down the source virtual machine
|
|
> * Shutting down the source virtual machine using Horizon dashboard
|
|
> * Disconnecting volume
|
|
> * Attaching volume to destination virtual machine
|
|
|
|
Some parts of some screenshots in this article are greyed out for privacy reasons.
|
|
|
|
Ensure that the transfer is possible[🔗](#ensure-that-the-transfer-is-possible "Permalink to this headline")
|
|
-----------------------------------------------------------------------------------------------------------
|
|
|
|
Before the actual transfer, you have to examine the state of the volume and of the instances and conclude whether the transfer is possible right away or should you perform other operations first:
|
|
|
|
### Projects must be on the same cloud[🔗](#projects-must-be-on-the-same-cloud "Permalink to this headline")
|
|
|
|
If the projects are not on the same cloud, do not use this article but see one of these articles instead: |