Managing your cloud resources with OpenStack: Difference between revisions

Cloning is the recommended method for copying volumes. While it is possible to make an image of an existing volume and use it to create a new volume, cloning is much faster and requires less movement of data behind the scenes. This method is handy if you have a persistent VM and you want to test out something before doing it on your production site. It is highly recommended to shutdown your VM before creating a clone of the volume as the newly created volume may be left in an inconsistent state if there was writing to the source volume during the time the clone was created. To create a clone you must use the [[OpenStack Command Line Clients|command line client]] with this command

Before detaching a volume it is important to make sure that the operating system and other programs running on your VM are not accessing files on your volume. If programs are modifying the contents of files on the volume when it is detached, the volume can be left in a corrupted state. Additionally if programs are reading files when a volume is detached it can result in unexpected behaviours of those programs. To ensure files are not being accessed shutdown the VM while you detach the volume. If you would prefer to avoid shutting down the VM, a successful [[Using_a_new_empty_volume_on_a_Linux_VM#Unmounting_a_device|unmounting of the volume]] will also ensure that no files are being accessed before detaching the volume.