Guide: Rescue and Recovery: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
=== Optionally: Restore the Original Instance === | === Optionally: Restore the Original Instance === | ||
* Copy a new SSH public key into the original VM's authorized_keys file. | * Copy a new SSH public key into the original VM's '''authorized_keys''' file. | ||
* Reverse the procedure above to rebuild the original instance. | * Reverse the procedure above to rebuild the original instance. | ||
Revision as of 17:35, 21 October 2025
Restore Access to VM
In some cases, you may lose access to a running virtual machine (VM) — for example, if your SSH key is missing. This guide explains how to recover your data or restore access to the instance.
Before proceeding, make sure the issue is not caused by network problems (e.g., security group misconfiguration or floating IP changes). If you've confirmed that it's not a network issue, follow the steps below. These steps can be carried out via the Dashboard or the CLI.
Recovery Procedure
- Stop the affected VM (e.g.,
foo1_vm). - Ceate a snapshot image of the instance and name it (e.g.,
foo1_img). - Use
foo1_imgto create a new volume, e.g.,foo1_vol. - Launch a fresh VM (e.g.,
foo2_vm) using a known working key pair. - Attach
foo1_voltofoo2_vmand mount its file system (this contains the original VM’s disk).
At this point you can recover your data from the mounted volume.
Optionally: Restore the Original Instance
- Copy a new SSH public key into the original VM's authorized_keys file.
- Reverse the procedure above to rebuild the original instance.