Recover VMWare - Revision history

Admin at 10:45, 24 January 2019

2019-01-24T10:45:52Z

Admin at 10:44, 24 January 2019

2019-01-24T10:44:50Z

Admin at 17:17, 23 January 2019

2019-01-23T17:17:33Z

Admin at 17:14, 23 January 2019

2019-01-23T17:14:40Z

Admin at 17:13, 23 January 2019

2019-01-23T17:13:49Z

Admin at 17:00, 23 January 2019

2019-01-23T17:00:10Z

Admin at 16:19, 23 January 2019

2019-01-23T16:19:09Z

Admin: Created page with "This page has detailed steps on how to recover VMWare machines that have been imported into NetBackup. NOTOC ==='''Step 1'''=== Login to the NetBackup GUI and navigate to..."

2019-01-23T16:04:25Z

Created page with "This page has detailed steps on how to recover VMWare machines that have been imported into NetBackup. __NOTOC__ ==='''Step 1'''=== Login to the NetBackup GUI and navigate to..."

New page

This page has detailed steps on how to recover VMWare machines that have been imported into NetBackup.
__NOTOC__
==='''Step 1'''===
Login to the NetBackup GUI and navigate to '''Backup, Archive and Restore''' section.

[[File:NBU-RestoreFiles.jpg]]

==='''Step 2'''===
Click on the '''Restore Files''' tab and select the Source Client, Destination and type of Policy to restore the VMWare backup files.
The '''Policy Type''' will be '''Standard''' as we are just restoring them as files.

[[File:VMWare-RestorePolicy.jpg]]

==='''Step 3'''===
Under '''Browse Directory''' select the Virtual Machine files to restore under the '''images''' folder.

[[File:VMWare-BrowseDirectory.jpg]]

==='''Step 4'''===
Choose to restore to a different location, and change the target destination to a temporary location on the NetBackup Server itself or to a shared location. In our case we used the location '''NBU_restore/VMWare'''.

[[File:VMWare-RestoreDirectory.jpg]]

@@ Line 52: / Line 52: @@
 {|style="padding: 5px; width: 85%;"
-| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' After restore of a Windows VM, you will need to install the latest version of VMWare tools for peripherals to work properly. If your ESXi host is unable to install the tools, the following VMWare article [https://kb.vmware.com/s/article/1036810 Unable to locate ISO for VMWare tools] will help resolve the issue.
+| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' After restore of a Windows VM, you will need to install the latest version of VMWare tools for peripherals to work properly. If your ESXi host is unable to install the tools, the following VMWare article [https://kb.vmware.com/s/article/1036810 '''''Unable to locate ISO for VMWare tools'''''] will help resolve the issue.
+|
 |}

@@ Line 49: / Line 49: @@
 ==='''Step 9'''===
-After registration, the VM is in a state to be Powered On.
+After registration, the VM can now be Powered On. You may need to specify to VMWare that the Virtual Machine has been copied from another Host when first Powered On.
 ----
 Use this link to go back to the main [[recoverydocs]] Page.

@@ Line 38: / Line 38: @@
 ==='''Step 7'''===
-Notice that the hard drive files would have been renamed to '''scsi0_0''', this file needs to be renamed to the  value of the flat.vmdk, '''i.e. CentOS6.8-flat.vmdk'''
+Notice that the hard drive files would have been renamed to '''scsi0_0''', this file needs to be renamed to the  value of the flat.vmdk, '''i.e. CentOS6.8-flat.vmdk'''.
 {|style="padding: 5px; width: 85%;"
@@ Line 49: / Line 49: @@
 ==='''Step 9'''===
-After registration, the VM is in a state to be powered on.
+After registration, the VM is in a state to be Powered On.
 ----
 Use this link to go back to the main [[recoverydocs]] Page.

@@ Line 41: / Line 41: @@
 {|style="padding: 5px; width: 85%;"
-| style="width: 1%;"|[[File:WArn.png|30px]]|| style="padding: 10px; width: 85%;"|'''Warning:''' If this step is not followed, the VM will fail to Turn On.
+| style="width: 1%;"|[[File:Warn.png|30px]]|| style="padding: 10px; width: 85%;"|'''Warning:''' If this step is not followed, the VM will fail to Turn On.
+|
 |}

@@ Line 38: / Line 38: @@
 ==='''Step 7'''===
-Notice that the hard drive files would have been renamed to '''scsi0_0''', this file needs to be renamed to the  value of the '''"flat.vmdk"'''. '''i.e. CentOS6.8-flat.vmdk'''
+Notice that the hard drive files would have been renamed to '''scsi0_0''', this file needs to be renamed to the  value of the flat.vmdk, '''i.e. CentOS6.8-flat.vmdk'''
 ----
 Use this link to go back to the main [[recoverydocs]] Page.

@@ Line 18: / Line 18: @@
 ==='''Step 4'''===
-Choose to restore to a different location, and change the target destination to a temporary location on the NetBackup Server itself or to a shared location. In our case we used the location '''NBU_restore/VMWare'''.
+Choose to restore to a different location, and change the target destination to a temporary location on the NetBackup Server itself or to a shared location. In our case we used the location '''/NBU_restore/VMWare'''.
 [[File:VMWare-RestoreDirectory.jpg]]
 ==='''Step 5'''===
-Re-create the folder for the Virtual Machine in the Datastore of an ESXi host, '''i.e. Datastore01/CentOS6.8'''
+Re-create the folder for the Virtual Machine in the Datastore of an ESXi host, '''i.e. /Datastore01/CentOS6.8'''
 [[File:VMWare-CreateDirectory.jpg]]
 ----
 Use this link to go back to the main [[recoverydocs]] Page.

← Older revision		Revision as of 16:19, 23 January 2019
Line 21:		Line 21:

	[[File:VMWare-RestoreDirectory.jpg]]		[[File:VMWare-RestoreDirectory.jpg]]
		+
		+	==='''Step 5'''===
		+	Re-create the folder for the Virtual Machine in the Datastore of an ESXi host, '''i.e. Datastore01/CentOS6.8'''
		+
		+	[[File:VMWare-CreateDirectory.jpg]]
		+
		+	----
		+	Use this link to go back to the main [[recoverydocs]] Page.