Snapshots
Table of Contents
- Types of snapshots
- Instance snapshot from the web interface
- Instance snapshot from the CLI
- Launching a snapshot from the web interface
- Launching a snapshot from the CLI
- Volume snapshot from the web interface
- Volume snapshot from the CLI
- Launching an instance from a volume snapshot
- General considerations
This article describes how to use snapshots to capture and store the file system state of a Pouta virtual machine.
Types of snapshots
There are two types of snapshots used in OpenStack: image (instance) snapshots and volume snapshots. Both snapshot types can be utilized when creating a new instance. Image snapshots are more common.
Instance snapshot from the web interface
Select 'Instances' tab, under 'Compute', from the left hand side menu (1). Select the virtual machine you want to take a snapshot of from the list and click the 'Create Snapshot' button in the 'Actions' column (2).
Give the snapshot a descriptive name (3) and click 'Create Snapshot' (4) to start the process.
You can access a list of snapshots from the 'Images' tab.
Instance snapshot from the CLI
Note
Ensure you have sourced the OpenStack RC file and can communicate with your OpenStack environment.
Use the following command to check the list of available instances:
$ openstack server list
The result should look something like this:
+--------------------------------------+--------------------+--------+---------------------------------------------+--------------+----------------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+--------------------+--------+---------------------------------------------+--------------+----------------+
| db2214e7-2175-4a82-9e3b-0a1892a6066a | important-linux-vm | ACTIVE | project_2007938=192.168.1.10, 86.50.230.174 | Ubuntu-22.04 | standard.small |
+--------------------------------------+--------------------+--------+---------------------------------------------+--------------+----------------+
Select the wanted instance, either by ID or name, and issue the following command:
$ openstack server image create --name important-linux-vm-snapshot-20320912-cli important-linux-vm
Here the name of the server instance was used instead of the ID. The name of the snapshot
can be defined with the --name parameter.
+------------+-------------------------------------------------------------------------------------------------------------------------------+
| Field | |
+------------+-------------------------------------------------------------------------------------------------------------------------------+
| created_at | 2032-09-12T08:05:39Z |
| file | /v2/images/5b92fd8b-d7e2-471c-bfbc-27c3041e54f7/file |
| id | 5b92fd8b-d7e2-471c-bfbc-27c3041e54f7 |
| min_disk | 80 |
| min_ram | 0 |
| name | important-linux-vm-snapshot-20320912-cli |
| owner | 124c43e4gafc46e4a18693b1a7ee47ed |
| properties | base_image_ref='41c7cd7e-8e10-4ced-a89e-41f159fe49fd', boot_roles='member,heat_stack_owner,creator', description='To find ... |
| protected | False |
| schema | /v2/schemas/image |
| status | queued |
| tags | |
| updated_at | 2032-09-12T08:05:39Z |
| visibility | private |
+------------+-------------------------------------------------------------------------------------------------------------------------------+
You can use the following command to check that the snapshot has been taken successfully:
$ openstack image list
The output of the command should look something like this:
+--------------------------------------+------------------------------------------+--------+
| ID | Name | Status |
+--------------------------------------+------------------------------------------+--------+
| 5c057d87-5353-4f3c-a7a9-bffbbb99da4c | CentOS-7 | active |
| 1585f871-f9c3-47ec-a3ff-1b80bce0b0eb | CentOS-7-Cuda | active |
| 500e4de4-23fb-4cc1-bac7-83c43a8cb7eb | CentOS-8-Stream | active |
| bef0ff50-1aaa-48af-95b2-910bf1da7dc9 | Ubuntu-18.04 | active |
| 5842526b-c835-4ad7-b572-4a8fe87752d1 | Ubuntu-20.04 | active |
| 41c7cd7e-8e10-4ced-a89e-41f159fe49fd | Ubuntu-22.04 | active |
| 3a9aad67-0f9c-4493-b574-17fe28d40afc | cirros | active |
| 14b2de4d-a5de-453a-bee0-f0b506198760 | important-linux-vm-snapshot-20320912 | active |
| 5b92fd8b-d7e2-471c-bfbc-27c3041e54f7 | important-linux-vm-snapshot-20320912-cli | active |
+--------------------------------------+------------------------------------------+--------+
Image snapshots hold the state of a given instance's root disk, and can typically be used as bootable images.
Warning
Possible ephemeral disk is not included in the snapshot.
Launching a snapshot from the web interface
Image snapshots are used just like any other image. You can launch one from the 'Images' view or from the 'Instances' view ('Launch Instance' button).
Enter the basic information for the new instance (1). Select 'Boot from snapshot' (2) as the boot source for the instance and to 'Instance Snapshot' select from the list of snapshots (3) the one you wish to launch.
Launching a snapshot from the CLI
A snapshot can also be launched from a command line using the following command:
$ openstack server create --flavor standard.small --image important-linux-vm-snapshot-20320912 important-linux-vm-RECOVERED
Last parameter of the command is the name of the new instance. Again, the output should be similar to the one below:
+-----------------------------+-----------------------------------------------------------------------------+
| Field | Value |
+-----------------------------+-----------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | |
| OS-EXT-STS:power_state | NOSTATE |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | None |
| OS-SRV-USG:terminated_at | None |
| accessIPv4 | |
| accessIPv6 | |
| addresses | |
| adminPass | DL5D7HESPahe |
| config_drive | |
| created | 2032-09-12T12:34:46Z |
| flavor | standard.small (d4a2cb9c-99da-4e0f-82d7-3313cca2b2c2) |
| hostId | |
| id | 288284b1-1bad-45ee-9e5e-fe56b40aacba |
| image | important-linux-vm-snapshot-20320912 (cf2b4ffb-b9a4-4937-abf7-9c461f778ce2) |
| key_name | None |
| name | important-linux-vm-RECOVERED |
| progress | 0 |
| project_id | 124c43e4efeb86e8a116e3fa174047ec |
| properties | |
| security_groups | name='default' |
| status | BUILD |
| updated | 2032-09-12T12:34:46Z |
| user_id | joonatol |
| volumes_attached | |
+-----------------------------+-----------------------------------------------------------------------------+
After launching a new instance from a snapshot (either from the web interface or the CLI) the 'Instances' view looks like below.
A few points to bear in mind:
- The new instance gets its own IP address if DHCP is used (1).
- Even though the SSH key pair is not shown in the Key Pair column for the new instance (2), it still exists because the snapshot is an exact copy of the old instance.
- Any bindings, e.g. to a public IP address, are not automatically changed from the old instance to the new one (3).
- Any volume mappings will also need to be reconfigured if you want to use them with the new instance.
Volume snapshot from the web interface
Select 'Volumes' tab, under Volumes, from the left hand side menu (1). Select the volume you want to take a snapshot of from the list and extend the 'Actions' menu. Choose the 'Create Snapshot' item from the list (2).
Give the snapshot a descriptive name (3) and click 'Create Volume Snapshot' (4) to start the process.
Volume snapshot from the CLI
Use the following command to check the list of available volumes:
$ openstack volume list
The result should look something like this:
+--------------------------------------+---------------+-----------+------+-------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+---------------+-----------+------+-------------+
| 27698e6c-92e2-41b6-bd6f-667a17495c3d | backup-volume | available | 100 | |
+--------------------------------------+---------------+-----------+------+-------------+
Select the wanted volume, either by ID or name, and issue the following command:
$ openstack volume snapshot create --volume backup-volume snapshot-of-a-backup-volume-cli
specifying the name of the snapshot as a last argument. The command produces following output:
+-------------+--------------------------------------+
| Field | Value |
+-------------+--------------------------------------+
| created_at | 2032-09-12T14:03:09.496299 |
| description | None |
| id | 890c4b19-44e6-4b6e-88a7-1806d6d8e3e1 |
| name | snapshot-of-a-backup-volume-cli |
| properties | |
| size | 100 |
| status | creating |
| updated_at | None |
| volume_id | 27698e6c-92e2-41b6-bd6f-667a17495c3d |
+-------------+--------------------------------------+
To list all volume snapshots, use the command:
$ openstack volume snapshot list
to get the following kind of listing:
+--------------------------------------+---------------------------------+-------------+-----------+------+
| ID | Name | Description | Status | Size |
+--------------------------------------+---------------------------------+-------------+-----------+------+
| 890c4b19-44e6-4b6e-88a7-1806d6d8e3e1 | snapshot-of-a-backup-volume-cli | None | available | 100 |
| 53f74334-54c1-41fa-bfde-4bbb41a36900 | snapshot-of-a-backup-volume | | available | 100 |
+--------------------------------------+---------------------------------+-------------+-----------+------+
Launching an instance from a volume snapshot
If certain requirements are met (the volume snapshot is bootable, contains a bootable operating system etc.), a new instance can be launched from the volume snapshot.
Again launching a volume snapshot instance works just like launching any other image.
Enter the basic information for the new instance (1). Select 'Boot from volume snapshot (creates a new volume)' (2) as the boot source for the instance and to 'Volume Snapshot' select from the list of snapshots (3) the one you wish to launch.
Launching a server image from a volume snapshot using the CLI is a slightly longer process and is not covered in this article. However, if you are interested, you can find more information in the official OpenStack documentation.
General considerations
We recommend powering off the instance and detaching volumes before taking snapshots. This is the best way to make sure the file system is captured in a consistent state.
Please note that snapshots may not always be the optimal method of getting an instance into a predefined state. For more robust solution, configuration automation tools such as Ansible and Puppet are recommended. Instead of using snapshots, these tools are used to create the environment from scratch and then restore the content of previous environment.
There is no limit to the number of snapshots you can take, but as a general courtesy you should keep snapshots to a minimum and remove unnecessary ones.