diff --git a/docs/background/.pages b/docs/background/.pages index e4b580231..6710222d1 100644 --- a/docs/background/.pages +++ b/docs/background/.pages @@ -4,6 +4,6 @@ nav: - "CCMP vs. OpenStack API": gui-vs-api.md - "Deleting projects": project-deletion.md - "Object storage": object-storage.md - - "Disaster recovery": disaster-recovery.md + - "Recovery service": recovery-service.md - kubernetes - Marketplace: marketplace.md diff --git a/docs/background/assets/disaster-recovery-option-manual-activation.png b/docs/background/assets/disaster-recovery-option-manual-activation.png index 773946783..f5d63538d 100644 Binary files a/docs/background/assets/disaster-recovery-option-manual-activation.png and b/docs/background/assets/disaster-recovery-option-manual-activation.png differ diff --git a/docs/background/assets/disaster-recovery-option-on-by-default.png b/docs/background/assets/disaster-recovery-option-on-by-default.png index ff842f115..453d440c2 100644 Binary files a/docs/background/assets/disaster-recovery-option-on-by-default.png and b/docs/background/assets/disaster-recovery-option-on-by-default.png differ diff --git a/docs/background/assets/recovery-service-controls.png b/docs/background/assets/recovery-service-controls.png new file mode 100644 index 000000000..ee6a63e0a Binary files /dev/null and b/docs/background/assets/recovery-service-controls.png differ diff --git a/docs/background/disaster-recovery.md b/docs/background/disaster-recovery.md deleted file mode 100644 index 32a72b19b..000000000 --- a/docs/background/disaster-recovery.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -description: What is the Disaster Recovery feature and why you want it ---- -# Disaster recovery - -When you [create a new server](../howto/openstack/nova/new-server.md) in {{brand}} you will notice an option named **Disaster recovery**, which is enabled by default. - -![Disaster recovery is enabled by default for new servers](assets/disaster-recovery-option-on-by-default.png) - -Even if you choose to disable it for a particular server, keep in mind that you have the option to enable it at a later time. - -![The disaster recovery feature can be manually activated for any server](assets/disaster-recovery-option-manual-activation.png) - -In the following, we explain what this option does, how it works in the background, and why you should consider enabling it. - -## What it is - -The *Disaster Recovery* (DR) feature is available via the {{gui}} and applies to servers and volumes that use our [Ceph](https://docs.ceph.com/) backend. -That would be **all** servers but the ones of the `s` [flavor](../reference/flavors/index.md#compute-tiers). - -## How it works - -As soon as you enable DR for a server or a single volume, you start getting snapshots for the corresponding [*RADOS Block Device* (RBD)](https://docs.ceph.com/en/latest/glossary/#term-Ceph-Block-Device) image. -Those snapshots are created automatically once per day, and you always have the snapshots of the last 10 days. - -Please keep in mind that all RBD snapshots are created in the same Ceph cluster and are not replicated remotely. -If, for any reason, you delete the original volume, then all snapshots will also be deleted, and the snapshot creation schedule will be canceled immediately. - -## Why enable it - -Provided snapshots are available, you can restore a server or a single volume to any of those snapshots. -For instance, you may discover that due to faulty application logic or simply a bug, you are now experiencing data corruption. -Then, one of your options would be to [go back in time](../howto/openstack/nova/restore-srv-to-snap.md) by restoring one of the available snapshots and keep going from there. - -## Restoration time - -You should know that the DR feature creates *point-in-time* snapshots on the storage level. -The time required to restore a server to a particular snapshot depends on its size. -During restoration, the server is shut off. -After the restore, you need to power the server back on manually. -Although this whole process takes time analogous to volume size, as we pointed out, we should also note that it only takes seconds to complete on average. diff --git a/docs/background/recovery-service.md b/docs/background/recovery-service.md new file mode 100644 index 000000000..323a9dcd2 --- /dev/null +++ b/docs/background/recovery-service.md @@ -0,0 +1,58 @@ +--- +description: What is the recovery service feature and why you want it +--- +# Recovery service + +When you [create a new server](../howto/openstack/nova/new-server.md) in {{brand}} you will notice an option named **Recovery service**, which is enabled by default. + +![Recovery service is enabled by default for new servers](assets/disaster-recovery-option-on-by-default.png) + +Even if you choose to disable it for a particular server, keep in mind that you have the option to enable it at a later time. + +![The recovery service feature can be manually activated for any server](assets/disaster-recovery-option-manual-activation.png) + +In the following, we explain what this option does, how it works in the background, and why you should consider enabling it. + +## What it is + +The *recovery service* feature is available via the {{gui}} and applies to servers and volumes that use our [Ceph](https://docs.ceph.com/) backend. +That would be **all** servers but the ones of the `s` [flavor](../reference/flavors/index.md#compute-tiers). + +## How it works + +As soon as you enable the recovery service for a server or a single volume, you start getting snapshots for the corresponding [*RADOS Block Device* (RBD)](https://docs.ceph.com/en/latest/glossary/#term-Ceph-Block-Device) image. + +Those snapshots are created automatically once per day. +By default, you have the snapshots of the last 10 days. +Optionally, you may choose to keep snapshots for the past 30 days. +The cost of a 30-day snapshot retention is 2× (**not** 3×) the cost of a 10-day snapshot retention. + +You can also make the snapshots immutable. +In that case, you will not be able to delete snapshots during the retention period manually. + +Keep in mind that you cannot delete a volume with snapshots. +So, as an example, if you have chosen a retention period of 30 days and also enabled immutability, then you will not be able to delete the volume before 30 days have passed. + +At any time, you may disable the recovery service, modify the retention period, or disable immutability for snapshots. + +![Recovery service, retention period, and immutability controls](assets/recovery-service-controls.png) + +Let's say, for instance, that you have enabled the recovery service and also the immutability feature for snapshots. +At some point, you want to change the retention period or disable immutability altogether; +you can do any of that. +Later on, you decide you do not need the volume anymore; +you disable the recovery service, wait for 10 or 30 days, and then delete the volume. + +## Why enable it + +Provided snapshots are available, you can restore a server or a single volume to any of those snapshots. +For instance, you may discover that due to faulty application logic or simply a bug, you are now experiencing data corruption. +Then, one of your options would be to [go back in time](../howto/openstack/nova/restore-srv-to-snap.md) by restoring one of the available snapshots and keep going from there. + +## Restoration time + +You should know that the recovery service feature creates *point-in-time* snapshots on the storage level. +The time required to restore a server to a particular snapshot depends on its size. +During restoration, the server is shut off. +After the restore, you need to power the server back on manually. +Although this whole process takes time analogous to volume size, as we pointed out, we should also note that it only takes seconds to complete on average. diff --git a/docs/howto/openstack/nova/assets/new-server/shot-01.png b/docs/howto/openstack/nova/assets/new-server/shot-01.png index 8b58442ad..5915600e4 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-01.png and b/docs/howto/openstack/nova/assets/new-server/shot-01.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-02.png b/docs/howto/openstack/nova/assets/new-server/shot-02.png index 2b0c04253..1dddd3cf4 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-02.png and b/docs/howto/openstack/nova/assets/new-server/shot-02.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-03.png b/docs/howto/openstack/nova/assets/new-server/shot-03.png index 772e86ee1..76f12ede7 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-03.png and b/docs/howto/openstack/nova/assets/new-server/shot-03.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-04.png b/docs/howto/openstack/nova/assets/new-server/shot-04.png index 2e28507cf..eafd37e0c 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-04.png and b/docs/howto/openstack/nova/assets/new-server/shot-04.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-05.png b/docs/howto/openstack/nova/assets/new-server/shot-05.png index c4a67a368..0154f3d51 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-05.png and b/docs/howto/openstack/nova/assets/new-server/shot-05.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-06.png b/docs/howto/openstack/nova/assets/new-server/shot-06.png index adf2349f6..8fcb7cef8 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-06.png and b/docs/howto/openstack/nova/assets/new-server/shot-06.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-07.png b/docs/howto/openstack/nova/assets/new-server/shot-07.png index 75d167a95..e5801c1f0 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-07.png and b/docs/howto/openstack/nova/assets/new-server/shot-07.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-08.png b/docs/howto/openstack/nova/assets/new-server/shot-08.png index 24cb19deb..b3b222b4b 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-08.png and b/docs/howto/openstack/nova/assets/new-server/shot-08.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-09.png b/docs/howto/openstack/nova/assets/new-server/shot-09.png index 72da4abee..42bc87472 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-09.png and b/docs/howto/openstack/nova/assets/new-server/shot-09.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-10.png b/docs/howto/openstack/nova/assets/new-server/shot-10.png index 86139b33d..828563772 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-10.png and b/docs/howto/openstack/nova/assets/new-server/shot-10.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-11.png b/docs/howto/openstack/nova/assets/new-server/shot-11.png index 25919fead..c195328b2 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-11.png and b/docs/howto/openstack/nova/assets/new-server/shot-11.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-12.png b/docs/howto/openstack/nova/assets/new-server/shot-12.png index 04059c450..1ba4c430f 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-12.png and b/docs/howto/openstack/nova/assets/new-server/shot-12.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-13.png b/docs/howto/openstack/nova/assets/new-server/shot-13.png index bc015272d..5fcbfa2a2 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-13.png and b/docs/howto/openstack/nova/assets/new-server/shot-13.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-14.png b/docs/howto/openstack/nova/assets/new-server/shot-14.png index 7dbe5ee87..ad3d6b8f4 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-14.png and b/docs/howto/openstack/nova/assets/new-server/shot-14.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-15.png b/docs/howto/openstack/nova/assets/new-server/shot-15.png index 494024c62..d9ab7ef73 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-15.png and b/docs/howto/openstack/nova/assets/new-server/shot-15.png differ diff --git a/docs/howto/openstack/nova/assets/new-server/shot-16.png b/docs/howto/openstack/nova/assets/new-server/shot-16.png index dad7e012c..13258bb16 100644 Binary files a/docs/howto/openstack/nova/assets/new-server/shot-16.png and b/docs/howto/openstack/nova/assets/new-server/shot-16.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/all-volumes.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/all-volumes.png new file mode 100644 index 000000000..144c06a4c Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/all-volumes.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-and-id.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-and-id.png new file mode 100644 index 000000000..cef43ce6f Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-and-id.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-details.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-details.png new file mode 100644 index 000000000..81fca15af Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-details.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-recovery-service.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-recovery-service.png new file mode 100644 index 000000000..d96d59764 Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/backing-volume-recovery-service.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-available-snaps.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-available-snaps.png deleted file mode 100644 index 50a337b73..000000000 Binary files a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-available-snaps.png and /dev/null differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-boot-from-snapshot.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-boot-from-snapshot.png deleted file mode 100644 index 6f1e9b907..000000000 Binary files a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-boot-from-snapshot.png and /dev/null differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-permission-to-proceed.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-permission-to-proceed.png deleted file mode 100644 index 6c53241d6..000000000 Binary files a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-permission-to-proceed.png and /dev/null differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-recover-in-progress.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-recover-in-progress.png deleted file mode 100644 index cdb9c3d66..000000000 Binary files a/docs/howto/openstack/nova/assets/rest-srv-to-snap/disaster-recovery-recover-in-progress.png and /dev/null differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/recovery-service-tab.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/recovery-service-tab.png new file mode 100644 index 000000000..77bf4a2f0 Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/recovery-service-tab.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-complete.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-complete.png new file mode 100644 index 000000000..d204914e7 Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-complete.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-latest-snapshot.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-latest-snapshot.png new file mode 100644 index 000000000..f596f8c5c Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-latest-snapshot.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-old-snapshot.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-old-snapshot.png new file mode 100644 index 000000000..5709b9a11 Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/restore-old-snapshot.png differ diff --git a/docs/howto/openstack/nova/assets/rest-srv-to-snap/volume-restored-create-server.png b/docs/howto/openstack/nova/assets/rest-srv-to-snap/volume-restored-create-server.png new file mode 100644 index 000000000..b847b82a3 Binary files /dev/null and b/docs/howto/openstack/nova/assets/rest-srv-to-snap/volume-restored-create-server.png differ diff --git a/docs/howto/openstack/nova/boot-image-volume.md b/docs/howto/openstack/nova/boot-image-volume.md index ffef293a9..89a2bc757 100644 --- a/docs/howto/openstack/nova/boot-image-volume.md +++ b/docs/howto/openstack/nova/boot-image-volume.md @@ -276,9 +276,9 @@ In the following, we show how to perform the conversion using the {{gui}} or the ![Choosing a flavor](assets/bfi-to-bfv/shot12.png) - Consider leaving the [*Disaster recovery*](../../../background/disaster-recovery.md) option enabled, and see if you want an external IP address for the server. + Consider leaving the [*Recovery service*](../../../background/recovery-service.md) option enabled, and see if you want an external IP address for the server. - ![Enabling disaster recovery and asking for external IP](assets/bfi-to-bfv/shot13.png) + ![Enabling the recovery service and asking for external IP](assets/bfi-to-bfv/shot13.png) Select the *default* security group and choose a *keypair* for the server. diff --git a/docs/howto/openstack/nova/new-server.md b/docs/howto/openstack/nova/new-server.md index 60251f513..86114d04d 100644 --- a/docs/howto/openstack/nova/new-server.md +++ b/docs/howto/openstack/nova/new-server.md @@ -5,7 +5,6 @@ description: How to create a new virtual server in Cleura Cloud Once you have an [account in {{brand}}](../../getting-started/create-account.md), you can create virtual machines --- henceforth simply _servers_ --- using either the {{gui}} or the OpenStack CLI. -Let us demonstrate the creation of a new server, following both approaches. ## Prerequisites @@ -25,7 +24,7 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f Notice all these rounded boxes on that pane, each for defining, configuring, and instantiating a different {{brand}} object. Go ahead and click the _Server_ box. - + Another pane, titled _Create a Server_, slides over. At the top, type in a name for the new server and select one of the available regions. @@ -39,11 +38,11 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f If that network is dual-stack or has one IPv4-based subnet, you may want the server to be publicly accessible via an IPv4 address. In that case, make sure to activate the _Connect a floating IP to the server_ switch. Then, use the dropdown menu below to set the _Create External IP on_ parameter to the network you have already attached the server to. - + Now, pay attention to the _Server profile_ parameter. - + ![Select server profile](assets/new-server/shot-04.png) - + From the corresponding dropdown menu, you must select a profile. Currently, the following profiles are available: @@ -57,13 +56,13 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f * the _Generic_ profile is for general-purpose cloud servers, * the _High CPU_ profile is for servers designed to host CPU-intensive applications, and - * the _Low Latency Disk_ profile is for servers that use a local low-latency disk. + * the _Low Latency Disk_ profile is for servers created over a local low-latency disk. We should point out that some profiles may not be available in all regions. Choose the _Generic_ profile for now, which is available in any of the regions. In the _Boot source_ section below, click the dropdown menu on the left and make sure you select _Image_, so you can choose one of the readily available OS images to boot the new server off of. - + ![Select boot source and image](assets/new-server/shot-05.png) To pick a specific image, click on the dropdown menu on the right. @@ -90,29 +89,37 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f You may leave the root device size unchanged, or modify it to be a bit higher than the default. When, at a later time, you decide to delete the server, you can do so but **keep** its boot volume (you may want, for example, to attach that volume to a new server). - Just disable the _Delete on termination_ option if you want this kind of flexibility. + Disable the _Delete on termination_ option if you want this kind of flexibility. On the other hand, if you want your root volume to be automatically deleted when the server is deleted, the _Delete on termination_ option is already enabled for you. In any case, use this option with caution. - + ![Boot target, volume, and volume size](assets/new-server/shot-07.png) - + Also, notice the _Storage classes (types)_ parameter, which actually deals with [volume types](../../../reference/volumes/index.md). By default, this parameter is set to _cbs_. - You may want to leave the _Disaster recovery_ option enabled. + Next, you may choose to leave the _Recovery service_ option enabled. If you do, then daily server snapshots will be created, and you will have the option for easy and fast roll-ups to previous snapshots. - Please be aware that leaving this option enabled increases the server's monthly estimated cost (again, it is displayed in the green rectangular area at the top). - ![Disaster recovery option](assets/new-server/shot-08.png) + Take note of the _Retention Days_ parameter, which by default is set to 10 days; + that means that each snapshot will be kept for 10 days, and only then deleted automatically. + + You also have the option to enable the _Immutable_ switch. + By doing so, you will not be able to manually delete snapshots before the retention period is over. + Also, you will not be able to delete the server volume until all immutable snapshots are deleted. + + Please be aware that enabling the recovery service increases the server's monthly estimated cost (again, it is displayed in the green rectangular area at the top). + + ![Recovery service option](assets/new-server/shot-08.png) To control network access to the server, use the dropdown menu to the right of [_Security Groups_](../neutron/create-security-groups.md) and choose one. ![Choose a security group](assets/new-server/shot-09.png) If you already have one or more key pairs in your {{brand}} account, you can now select a public key to be included in the `~/.ssh/authorized_keys` file of the server's default user. - (For the image you have selected, that user would be `ubuntu`.) + (For the image you have selected, that would be the `ubuntu` user.) That way, you can securely log into the remote user's account via SSH without typing a password. - + ![Indicate an existing keypair](assets/new-server/shot-10.png) In case there are no key pairs to choose from, activate the _Set password_ option and set a password for the default user account (`ubuntu`). @@ -122,12 +129,13 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f A configuration script is automatically prepared based on the choices you have already made. That script runs during system boot and performs housekeeping tasks like user account creation, enabling acceptable authentication methods, and configuring remote package repositories. Click on _Advanced Options_ to see the default script. + Also, optionally enable the _Upgrade packages_ option, so any available package upgrades are applied during system boot. ![Default server configuration script and user data propagation method](assets/new-server/shot-12.png) Regarding the _User-data propagation method_ above, notice that the _Use metadata service_ is pre-selected for you. For more on what this is and why you might want to select the _Use configuration drive_ method, please read our guide on [launching a server with a configuration drive](config-drive.md). - + It is now time to create your {{brand}} server. Click the green _Create_ button, and the new server will be readily available in a few seconds. @@ -314,7 +322,7 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f ## Viewing information about the newly created server === "{{gui}}" At any time, from the {{gui}} you may see all servers, and get detailed information regarding each one of them. - Expand the left-hand side vertical pane, click _Compute_, then _Servers_, and, in the central pane, select the region you want. + Expand the left-hand side vertical pane, click _Compute_, then _Servers_, and, in the central pane, select the region and the server you want. ![View server details](assets/new-server/shot-14.png) === "OpenStack CLI" @@ -333,7 +341,7 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f === "{{gui}}" While viewing information regarding your server, you may get its IPv6 or public IPv4 address (e.g., from the _Addresses_ tab), and connect to it remotely via SSH. Alternatively, you may launch a web console and log in. - Click on the three-dot icon on the right of the server header, and from the pop-up menu that appears, select _Remote Console_. + Click the orange :material-dots-horizontal-circle: icon on the right of the server row, and from the pop-up menu that appears, select _Remote Console_. ![Launch remote console](assets/new-server/shot-15.png) @@ -348,5 +356,5 @@ On the other hand, if you prefer to work with the OpenStack CLI, please do not f openstack console url show zug ``` - Usage of the web console is discouraged, though. - Instead, securely connect to your server via SSH. +Usage of the web console is discouraged, though. +Instead, securely connect to your server via SSH. diff --git a/docs/howto/openstack/nova/restore-srv-to-snap.md b/docs/howto/openstack/nova/restore-srv-to-snap.md index 64f29ce5e..fa4620c80 100644 --- a/docs/howto/openstack/nova/restore-srv-to-snap.md +++ b/docs/howto/openstack/nova/restore-srv-to-snap.md @@ -3,30 +3,59 @@ description: How to restore a server to a particular snapshot --- # Restoring a server to a snapshot -Servers in {{brand}} that have the [disaster recovery](../../../background/disaster-recovery.md) feature enabled can go back in time, meaning you may restore such a server to one of the available point-in-time snapshots. +Servers in {{brand}} that have the [recovery service](../../../background/recovery-service.md) feature enabled can go back in time, meaning you may restore such a server to one of the available point-in-time snapshots. Here is how you can do that. ## How to restore, step by step To select a particular snapshot and restore your server to it, first off, navigate to the {{gui}}. -From the left-hand side vertical pane, choose Compute → [Servers](https://{{gui_domain}}/compute/servers), then expand the detailed view of the server of interest. -Select the *Disaster Recovery* tab and see all available snapshots listed below. -For each one of those, the date and creation time are visible. +From the left-hand side vertical pane, choose Compute → [Servers](https://{{gui_domain}}/compute/servers). +In the central pane of the {{gui}}, locate the server of interest. +Click its row to bring all server details into view, then go to the *Recovery Service* tab. -![All available snapshots for selected server](assets/rest-srv-to-snap/disaster-recovery-available-snaps.png) +![The Recovery Service tab of the server of interest](assets/rest-srv-to-snap/recovery-service-tab.png) -Click on the snapshot you want. -A pop-up window will appear, asking for your permission to proceed. -Make sure this is indeed the snapshot you want, then click the red button labeled *Yes, Restore snapshot*. +Notice the _Backing volume_ and its ID. +Click the ID, and in the pop-up window that appears, select _View Details_. -![Asking for permission to restore snapshot](assets/rest-srv-to-snap/disaster-recovery-permission-to-proceed.png) +![Backing volume and its ID](assets/rest-srv-to-snap/backing-volume-and-id.png) -The restore process will begin immediately. -You can tell it is progressing by checking the status. +A new pop-up window appears, displaying details about the server volume. +Select the _Recovery Service_ tab. -![Snapshot recovery in progress](assets/rest-srv-to-snap/disaster-recovery-recover-in-progress.png) +![Backing volume details](assets/rest-srv-to-snap/backing-volume-details.png) -As soon as the snapshot is ready to be used, you will see a message indicating that it has started. -Do not forget to activate the server; click on its row to select it, then click the :fontawesome-solid-play: button above. +You now see all available volume snapshots. +You may restore the server to any of those. +Go ahead and click on the _Restore_ option of the latest snapshot. -![Start server to the snapshot](assets/rest-srv-to-snap/disaster-recovery-boot-from-snapshot.png) +![Backing volume snapshot list](assets/rest-srv-to-snap/backing-volume-recovery-service.png) + +A new window named _Restore Snapshot_ appears. + +If the snapshot you are about to restore comes from a boot volume, like in the example here, then you can only restore the snapshot to a **new** volume. + +Had you chosen to restore an **older** snapshot, then you could also restore it to a **new** volume. + +The only time you can restore a snapshot to an existing volume is when the snapshot comes from a non-boot volume and is the newest. + +To restore the selected snapshot, click the green _Restore_ button. + +![About to restore the latest snapshot](assets/rest-srv-to-snap/restore-latest-snapshot.png) + +Restoring a snapshot may take some time, but in many cases the operation completes after a few seconds. +Check the messages at the bottom of the window for the latest restore jobs. + +![Snapshot restoration complete](assets/rest-srv-to-snap/restore-complete.png) + +To see the new snapshot, from the left-hand side vertical pane of the {{gui}} choose Storage → [Volumes](https://{{gui_domain}}/storage/volumes). + +You can spot the new volume by looking at the _name_ column; +its name is prefixed by "Restored" and immediately followed by the ID of the original volume. + +![All volumes, including one created from a snapshot](assets/rest-srv-to-snap/all-volumes.png) + +You can now create a server from the new volume. +Click the orange :material-dots-horizontal-circle: icon at the left of the volume row, select _Create Server_, and work as you usually would while [creating a new server](new-server.md). + +![Creating a server from the new volume](assets/rest-srv-to-snap/volume-restored-create-server.png) diff --git a/docs/reference/limitations/openstack.md b/docs/reference/limitations/openstack.md index 306eb2323..4ba26688e 100644 --- a/docs/reference/limitations/openstack.md +++ b/docs/reference/limitations/openstack.md @@ -26,7 +26,7 @@ It also means that you cannot use the following `openstack` CLI commands; they a {{brand}} does not support the OpenStack volume backup service (`cinder-backup`). -For automated, scheduled volume *snapshots,* consider configuring your servers for [Disaster Recovery (DR)](../../background/disaster-recovery.md) via the {{gui}}. +For automated, scheduled volume *snapshots,* consider enabling the [recovery service](../../background/recovery-service.md) for your servers. ## Glance diff --git a/mkdocs.yml b/mkdocs.yml index 595a8b7cd..04dc36296 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -94,6 +94,7 @@ plugins: cards: !ENV [DOCS_ENABLE_SOCIAL_CARDS, True] - redirects: redirect_maps: + 'background/disaster-recovery.md': 'background/recovery-service.md' 'howto/account-billing/change-billing-data.md': 'howto/account-billing/change-account-data.md' repo_url: https://github.com/cleura/docs site_name: "Cleura Docs"