[Action of the Virtual Machine] During the Recovery Boot (Restart)

Action of the Virtual Machine

During Recovery Boot (Restart)

STEP 1: Select the virtual machine
In the lefthand menu, click on “Virtual Machines” then click on the appropriate virtual machine from the list that you wish to recover.

Select_VM.png

 

STEP 2: Reboot in Recovery
Click the “Startup on Recovery” in the action items. In the case where the virtual machine is running this is refered to as “Reboot in Recovery”.

Reboot_in_Recovery.png

 

STEP 3: Confirmation Screen
Pop-up for recovery mode boot (restart) will appear. Please click “OK” to confirm.

Please note that you cannot login using the normal password. Use these credentials:

User account: root
Password: recovery

Notification.png

 

STEP 4: How to check the recovery mode
You can confirm that the server is in recovery mode by accessing the server through the SSH terminal emulator or you can log in with recovery mode credentials from STEP 3.

 

STEP 5: Connection to the virtual machine from recovery mode
How to connect to the virtual server when up and running in recovery mode.

Access the virtual server that was launched in the recovery mode with the (SSH) Terminal emulator

Login as: root
root@****.****.****.****'s password: recovery

To reconnect to the actual virtual machine, use the mount command.

The mount command
This is a command available in linux for the filesystem and the peripheral devices. This time, a recovery mode virtual server(USB) is used to mount(connect) the actual virtual machine.

[root@onapp ]# mount /dev/sdb1/mnt

The sbd1 shown here refers to the primary disk of the actual server. (The hypervisor type is Xen in this manual). This mounts(connects) the primary disk of the actual virtual machine.

[Hypervisor: Xen]

/ sdb1 Primary disk
/ sdb2 Swap disk
/ sdb3 It's the assigned /sdb 3. the added disks after setting virtual server, 4 and 5

[Hypervisor:KVM] – Not Available for US

/hdb1: Primary disk
/hdb2: Swap disk
/hdb3: Assigned / hdb3, the added disk after setting virtual servr, 4 and 5.

Confirm that you can actually connect to /sdb1. Confirm using the df command. The output is as below: / dev/sdb1 is displayed if there is a successful connection.

[root@onapp ~] # df -h
Filesystem size used avail use% Mounted on
/dev /mapper /live-rw 4.0G .1G 3.0G 37% /
tmpfs 1.3G 9 1.3G 0% /dev /shm
/dev/sdb1 9.9G 2.3G 7.2G 24% /mnt

If successfully connected to a virtual machine you can modify configuration files and look for the information you need to retrieve and/or check if necessary.

 

 

Note: GMO CLOUD AMERICA INC. does not make any guarantee with regard to the content of this manual and will not be held responsible for any damages resulting from customers or third parties.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk