INSTRUCTIONS VEEAM BACKUP & REPLICATION 9.5B RESTORE VM ON VMWARE VSPHERE VCENTER PART 3

0
262
Image 5 19

Summary


You can review the previous sections here:

Part 1: INSTRUCTION TO INSTALL VEEAM BACKUP & REPLICATION 9.5B PART 1

Part 2: CONFIGURATION GUIDE VEEAM BACKUP & REPLICATION 9.5 B PART 2

Part 3: INSTRUCTIONS VEEAM BACKUP & REPLICATION 9.5B RESTORE VM ON VMWARE VSPHERE VCENTER PART 3

Context

A broken virtual machine (VMSRVPANEL01) Centos7 fails to boot up

Image 5


Assuming the error cannot enter the OS, now proceed to restore the operating system

First, Shutdown VM

Image 6

Requirement

VM must be backuped

RESOTORE MODE

Instant VM Recovery

Veem Backups back up Home-> Backup->Disk select Job name to Restore

Image 7

Select Instant VM Recovery to test before recovery. Due to broken OS we can restore the Entire VM.

Explain more Instant VM Recovery: this mode allows quick recovery for testing or emergency, the mechanism is that the Veeam server register VM needs to be restored to Vcenter or Esxi host and will mount the VM from Veeam to run so it will be very fast, about If it is stored, the datastores are in Veeam.

Here we choose the time of restore, we get the nearest date offline

Image 8

Restored to the orginal location: Restored properly at the VM root

Restored to new Location Or different Settings: Restore the VM to another directory or to other configurations.

In this lab, I selected the root directory for example, but actually should choose new location when we are ok, we choose the root directory again.

Image 9
Image 10

Select applied network connection and open offline

Image 12

Select Restore offline. Because I restored to the same location, Veeam will delete the VM before restoring

Image 13


Here we see

Image 14

The VM was immediately started immediately. Can run always or then we restore

Image 15


This means that the VM can quickly recover the Veeam that has mounted the VM running on the old host. And we have to proceed with the migration too.

Image 16

 Waiting for user to start migration


Instant VM Recovery: It can be understood that the test environment before being restored

Let miration select stop session and select restore entire VM, which means restoring the entire VM

Image 17
Image 18
Image 19

Restore Entire VM

Now we proceed to restore full offline similar to the steps in the vm instant restore offline

Image 20
Image 21


Choose to restore the original always

Image 22


Note Reason

Image 23
Image 24


The process will perform a full VM root recovery.


This step will mount and copy from the Veeam backup to the esxi datastored, unlike the instant step just mount and the datastore is in the Veeam backup.

Image 25
Image 26
Image 27

Restore takes about 13 minutes with a virtual machine running up. Time depends on network speed, virtual machine capacity, and number of disk read and write data of datastores

Check again Esxi has successfully restored

Image 28
Image 29

Good luck

Restore Virtual Disk


Meaning this level allows recovery at the virtual machine file level * .vmdk in the VM folder.

In case the virtual machine is broken, it is not enough to restore all the virtual machine as the first case. We can either restore the vmdk file and re-create another server or mount the old server to run.

Image 30


Select the nearest date for example 02/08/2020

Image 31


Select restore file * .vmdk to datastores and restore type disk should be the same as default

Image 32
Image 33
Select yes and next
Image 34
Image 35
Check on target VM after restoring.


Wait for the recovery process

Image 37


Restore ok, it takes about 19:20


Re-start the VM and reboot to see the results.

Image 38
We have successfully restored

Restore file Virtual Machine Files

This means that it is allowed to restore at the virtual machine file level (VM files (* .vmdk, .vmx and files) in the VM folder. or corrupt files in the datastore.

Regarding the restore mechanism, it will load the image-leve block backup. Veeam Data Movers will read from the backup resposities and the backup proxy returns the VM File and the copy returns the root directory location folder in the VM datastore or the specified save location.


Contextual simulator


I accidentally or the problem corrupte file config * .vmx

Image 39
Image 42


Error did not find the path

Image 43


Then perform a restore

Home-> disk->Job name and VM

Image 44


Choose the latest backup date

Image 45


We just need to select a * .vmx file to recover. And choose the default save location then copy the file to the datastores

Image 46
Image 47
Image 48


The file is relatively light and will not take much time

Image 49


Next step we copy this file into the datastore of esxi to run

Image 50
Image 51
Image 52

If there is an error related to SSL CA, please click to trust esxi host to run

Image 53
Image 54
Image 55

Upload success again.


We need to register with vCenter or esxi to identify again

Image 56
Image 57
Image 58
Image 59


Retest Start and re-start the VM

Image 60
Image 61


Let’s Enjoy it


Good luck

Restored Guest Files

You can use IFLR (Instant File-Level Restore) to recover individual VM guest OS files and folders from VM backups and replicas. IFLR does not require you to extract the VM image to a staging location or start the VM prior to restore. You can restore files and folders directly from a regular image-level backup or replica to the necessary point in time.

IFLR works with any VM guest OS file system. Veeam Backup & Replication offers different tools and methods for different file systems:

  • Restore from FAT, NTFS or ReFS: for file-level restore from Microsoft Windows VMs with NTFS, FAT and ReFS file systems, you can use the File-Level Restore wizard.
  • Restore from Linux, Unix and Other File Systems: for file-level restore from Linux, Solaris, BSD, Novell Storage Services, Unix, Mac and other file systems, you can use the multi-OS File-Level Restore wizard.

Note that multi-OS file-level restore supports recovery of files and folders only. Recovery of other file system objects such as pipes is not supported.

  • Restore from Other File Systems: for file-level restore from file systems not supported by file-level restore wizards, you can leverage the Instant VM Recovery functionality.

Note: when restoring this type we need to note the option at Backup is to check the enable dectect application and logon to authenticate the admin level inside the application or Sql, Exchange, ..

Image 62

Context Restore data levels in the virtual machine. For example file server types in strings. The lab I am testing is linux so I will continue the context of the file inside linux.

The data /ect/my.cnf.d I deleted it by hand.

Image 63


Proceed to restore


Remember to have backup

Image 64


Choose the nearest date

Image 65
Image 66


The helper appliance program will load, for example, to choose a host running mount that runs the VM temp to get the file

Image 67
Image 68


Or we can restore to the appliance’s virtual FTP server.


We see green check means that it satisfies FLR condition.

Image 69

Select Finish after 20s the VM will boot up

Image 70

Wait a little Backup will load FLR program offline

Image 71


Note we have to select the * .vmdk-> sda1 file to have the boot file because this part is located in a separate partition sda1, and for normal files we choose go to LVM-> centos-root-> boot. Here, it is possible to load the files we deleted or corupt.


Select the deleted folder /etc/my.cnf.d=> restore-> overwrite or we can copy it out and transfer it to the VM.

Image 72


In case you cannot choose the VM, we just give you the link

Image 73

If you need to root authentication of the VM we log in to access it.

Image 74


Let’s wait a bit for Server Veam to work loading and recovering files.


Let’s wait a bit for Server Veam to work loading and recovering files.

Image 75
Image 76
Image 77
Image 78
Image 79


Restore finished we copy winscp copy into Linux offline


There are also some types of recovery via Azue, Amazon EC2, because there are no conditions, so the Admin only works here, .. or export or extract the .vbk file, .. You can save yourself.


Good luck to you

The following I will guide on Hyper-V okay. Please look forward to it

Previous articleMindjet MindManager 2020 v20.1.233 Win / 12.1.190 macOS
Next articlePotential data loss when using Instant VM Recovery
Phuong Nguyen
Hi, Nguyen Van Phuong is the owner of the website viettechgroup.vn. I 've been working in the IT sector since 2008. With nearly 12 years experience in the fields of design development, Governance, operating system enterprise network infrastructure.. I'm now a senior Infrastructure Administrator for the Enterprise network. Achivements: IT Project management IT management System and Network IT Security and data protection. Plan and bugged for Infrastructure and Security Deployment system Server (HP, IBM, Lenovo, Dell..), Network (Cisco, Juniper, Enterasys,..), PABX system, Firewall (Cisco ASA 5525-x, Juniper SSG520,..) Network system administration and maintenance: +Management all network configure IT system: AD, DNS, DHCP, Cores switch, Access switch, Router, Firewall, etc. Design & implement IT system, project management and manage IT operation, I also have extensive experience of ERP System base SQL , HRM, etc. Vendor/external system integrator management: support other department in terms of technical specifications for cost optimize, business process efficiency, procurement spend compliance. Virtualization System Deployment on Microsoft Windows Server 2016 (Hyper-V) and VMware ( Vmware vSphere 5.5, 6.5,6.7 vCenter) Backup and restore management on Symantec backup products (Veritas Backup 16, 20, 20.1, 20.2 ), Veeam Backup & Replication 9.0, 9.5U1, 9.5U2 U3, U4

LEAVE A REPLY

Please enter your comment!
Please enter your name here