Note an easy way to filter the volumes is to enter

This preview shows page 40 - 44 out of 50 pages.

NOTE:An easy way to filter the volumes is to enterbackupin the search field just above thegroup box. This will filter all volumes with “backup” in the name.Hover over the VeeamAUX volume to see the full name of this volume.
HPE Nimble Storage Backup with VeeamRev. 19.21L3-10Confidential – For Training Purposes OnlyTask 5: Verify the recovered VM in vSphere1.In the browser, open thevSphere Web Clienttab.2.In the Navigator panel, click theStorageview icon. Note that a new datastore namedsnap-xxx-DS-for-Bwas created. This is the clone volume from the array from Task 4. In the tree structure, clickthesnap-xxdatastore and then in the main window, click theFilestab. Notice that the VM-For-Backup directory is on this datastore. The folder name for a VM does not change unless a storagevMotion operation is performed. At that point vSphere renames the folder to match the VM name,unless the name already exists on a datastore.3.In the Navigator panel, click theVMs and Templateview icon.Note the new VM namedVM-For-Backup_recovered. This is the VM that Veeam just restored.In the tree structure, click theVM-For-Backup_recoveredVM and then in the main panel, click theSummarytab.Expand theVM Hardwareinformation panel and expandHard disk 1in this panel. Note that the diskis located on the snap-xxxdatastore. This is the clone of the backup snapshot.
HPE Nimble Storage Backup with VeeamRev. 19.21L3-11Confidential – For Training Purposes Only4.Note that the VM-For-Backup_recovered VM is powered on and running. If the original VM was inrunning status when the backup was made, a warning indicator would show that a VMware snapshotconsolidation would be required. This is because Veeam made a VM-consistent backup of the VMand you have recovered to that point. This lab does not cover VMware snapshot consolidationoperations.5.At this point, the administrator can run a test to make sure the data in the VM-For-Backup_recoveredVM is the correct data to restore to. Production users can now also start to use this VM. Theadministrator can also delete the old VM-For-Backup VM from the storage and rename the restoredVM to the original VM name, if required. For long-term use, it is a best practice to move the VM datato a production storage device rather than running the VM for a long time on the clone of thesnapshot.
HPE Nimble Storage Backup with VeeamRev. 19.21L3-12Confidential – For Training Purposes OnlyTask 6: Start migration to the production volume1.Return to the Veeam Backup and Replication management interface. ClickFinishto close theRecovery window if it is still open. Make sure theHomemenu is selected in the bottom left. From thetree structure in the top left, clickInstant Recovery. Note the recovery job waiting. Right-click therecovery job and note the options in the drop-down menu.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 50 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Spring
Professor
Jonny Terrory
Tags
Veeam

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture