After Uploading Vmdk to Datastore It Provisioned?

Know how to restore Datto Fill-in to VMWare VSphere using image export

This article provides a step-by-step tutorial to restore Datto backup to VMWare VSphere using image export. We will walk you through the steps where yous will consign a backup equally a VMDK, and motion it back to a permanent storage location within the VMware vSphere environment. This method does non provide thin or thin provisioning for the paradigm file that is written to your VMWare storage.

Please note that using VMWare Converter is the preferred method of restoring a system to a VMware vSphere environment, and supports a sparse provisioned transfer.  See hither for that procedure: Using VMWare Converter

Procedure

Before this procedure, you must follow steps in previous topic Consign Paradigm to make the VMDK consign bachelor on the network via NFS.

Warning: Do NOT use the "upload file/folder" button on the datastore browser to upload the vmdk and .datto paradigm file to your VMware vSphere surround. This could preclude certain vSphere features from working on a virtual car associated with these files. Instead, please use the procedure outlined in this article.

one. Starting vSphere

1) Launch the VMware vSphere Client to connect to the VMware ESXi Host or vCenter server, and log in.

Effigy 1 – Client Login

2) Once logged in to the vSphere Client, with the host selected, click the Configuration tab.

Figure 2 – Selecting the Configuration tab in the vSphere Customer

3) From the Configuration tab, select the Storage link listed under Hardware. Then, select the Add together Storage push button in the summit right corner of the window.

Figure 3 – Locations of Storage Hardware and Add Storage Links

2. Add together Storage Magician

i) In the Add Storage wizard, select Network File System, and then click the Next push button.

Effigy 4 – Selecting Network File System

two) The Network File System window that and so appears asks for the server and folder that you lot obtained from the steps in the Export Image article. Provide a datastore name, and click theNext button.

Figure 5 – Server, Folder, and Datastore Proper noun Locations

three) Ostend that the path to the NFS share on the Datto device is accurate, and select Stop to consummate the Add Storage wizard.

Effigy 7 – Finish the Add Storage Wizard

3. Copying the VMDK to a permanent datastore

Note: The below method copies a VMDK with thick provisioning considering of limitations to the VMWare GUI.  The VMDK tin be copied with sparse or thin provisioning using ESXi control line:

vmkfstools -i /vmfs/volumes/YourDataStoreName/C.vmdk -d thin /vmfs/volumes/DestinationDataStoreName/C.vmdk

i) Right-click on the datastore you just created, and click Scan Datastore. You lot will utilise this as the "source datastore" in the next steps.

Figure eight – Browse Datastore

2) Repeat the previous stride on the datastore you wish to use for the permanent location of the restored virtual machine. You will use this datastore as the "destination datastore" in the next steps.

Figure nine – Selecting Scan Datastore

iii) In the destination datastore, create a New Binder and proper name it accordingly.

Effigy 10 – Creating New Folder In Destination Datastore Browser

4) From the source datastore, select the VMDK, and select copy.

Figure xi – Select VMDK File from the Source Information Store

v) Paste the VMDK into the destination datastore.

Figure 12 – Paste VMDK from Source Data Store to Destination Information Store

6) A progress window comes up while the VMDK copies to the destination data store.

Figure thirteen – Re-create Progress to Destination Information Store

Note: The deejay epitome provided past the vmdk consign is thick-provisioned. Using the method above to copy the vmdk from the temporary NFS datastore to the permanent storage location will result in a thick-provisioned vmdk in the permanent destination datastore. If y'all wish wish to copy the vmdk as thin-provisioned, this must be done from the vSphere CLI using vmkfstools.

Warning: Exercise Non copy the .vmx file. The .vmx file should not be used to restore the system. Please follow the steps below to create a new virtual auto and attach the recovered .vmdk files to the new virtual car.

4. Creating a New Virtual Machine

1) Right-click on the host at the tiptop of the list of virtual machines, and select New Virtual Machine. Alternatively, press the key combination CTRL+Due north.

Figure 14 – New Virtual Machine… Wizard

2) Go through the wizard and configure the virtual machine accordingly.

3) When you get to the Select a Disksection, select Apply an existing virtual disk.

Effigy 15 – Using an Existing Virtual Disk

4) ClickBrowse.

Figure sixteen – Browsing to the Path of the VMDK on the Data Store

5) Select the datastore where the VMDK is located, and click Open. Select the VMDK of the boot book (this is typically C).

Figure 17 – Browsing a Information Store for VMDK

6) Once the VMDK has been mapped from the data store, click Side by side.

Effigy 18 – VMDK Selected

7) Click Adjacent, and click Finish.

8) Attach more existing disks every bit necessary by editing the virtual motorcar settings.

9) Boot the virtual server.

Note: If the virtualization fails afterward the get-go attempt, try some other storage controller for the virtualization. It also may be necessary to run HIR from the StorageCraft recovery surround in the outcome that the boot device is found inaccessible due to storage controller changes. Please contact support if this is the example.

Hopefully, you lot constitute this how-to article helpful and now you lot are able to restore Datto backup to VMWare VSphere using epitome export. If y'all need any further assistance, don't hesitate to accomplish out. Our staff is made up of Datto-Certified technicians.

adamspridn1966.blogspot.com

Source: https://invenioit.com/continuity/restore-datto-backup-to-vmware-vsphere-using-image-export/