Considerations

• If the Hybrid Workloads agent restarts during the file restore operation, the job is not retried as Druva does not store any guest OS credential. This job will fail with  PHOENIX250. For more information  see, Druva errors.
• The  target virtual machine should have enough space to store the restored files. If the target virtual machine does not have enough space, the triggered restore job will be marked as successful with error.
• File-level restore for deduplicated volume is not supported. Although it is possible to browse the disk successfully, it does not guarantee that files/folders can be restored successfully. As a workaround, you must restore the full VMDK.

Procedure

1. Log in to the Hybrid Workloads Management Console. 
2. From the top menu bar, select your organization if organizations are enabled. 
3. Click Protect > VMware. 
   The All vCenter/ESXi host page appears that lists all the registered vCenter/hypervisors. 
4. You can either select the registered vCenter/ESXi host from the card view or list view or select it from the vCenter/ESXi host list in the left navigation pane.
5. In the left navigation pane, click Configured VMs.
6. Select the virtual machine you want to restore.
7. Click Restore > VM Restore.
8. Click Data Restore and then select a recovery point.
   To know more about restoring cold recovery points, see Restoration of cold-tier data.
9. Click Files & Folders and select the file or folder you want to restore.
   

   Note: A single click of expanding a particular folder will load a total of 1024 files/folders. If there are more than 1024 files/folders, then the Load More option will be visible to display the next set of results in that folder.

   Suppose all the backup proxies for the source backup set vCenter or standalone ESXi host are in a disconnected state. In that case, you can still use a different vCenter or standalone ESXi host proxies that are in a connected state for file-level browse and restore. Select the alternate vCenter or standalone ESXi host for file-level and click Save. The file-level browse is triggered on the alternate vCenter or standalone ESXi host Backup proxy. 

    

    

   If the disk configured for the selected VM is a Dynamic GUID (Global Unique Identifier) Partition Table (GPT) disk, an error is displayed with a warning, for example, 

   Failed to mount 2 out of 4 volumes.

   
   
   File-level restore eliminates the need to perform time-consuming disk restores when you want to restore a single file. However, during file-level restore, the volumes listing is excluded for Dynamic GPT disks in the backup set. Therefore you can use a Windows Server staging VM to perform a file-level browse restore. 
   A staging VM can be another Windows Server VM present in your environment. For more information, see prerequisites for a staging VM. 

   Note: During FLR browse for restoring data from Linux VM, Druva considers and displays every logical partition as a separate volume. Also, the volume/mount point under the root is visible as an empty directory.

   Perform the following:

   1. Click Select Staging VM. The Select Staging VM dialog is displayed with various topology details. 
      

       

      Field	Description
      Destination vCenter	Select the required destination vCenter where you want to restore the files or, in the case of the CIFS share to which you intend to restore the files. Ensure that the Backup proxy installed on this vCenter can access the CIFS shares.
      Destination Hypervisor	Select the required hypervisor.
      Backup Proxy Pool	From the drop-down list, select a Backup proxy pool. It is recommended that you select a Backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore. Note: If the virtual machine has a Backup proxy pool mapped to it, the mapped Backup proxy pool is selected by default.
      Staging VM	Select a staging VM with credentials assigned or credentials not assigned.  If you select a staging VM without credentials, then the Credentials field is displayed. Note: This field lists the staging VMs only if it follows all the pre-requisites. Note: The staging VM is used to mount volumes for file-level restores to the target VM.
      Enter credentials for the selected staging VM
      Credentials	Select or enter credentials for the selected staging VM. If you click the Custom value, then you can create credentials and the Label, Username, and Password fields are displayed.
      Label	Enter a label for the staging VM.
      Username	Enter a valid username for the staging VM.
      Password	Enter a valid password for the staging VM.

   2. Click Save.

      Note: After you click Save, the Dynamic GPT disks browse workflow is started. A browse job is triggered on the Backup proxy that mounts the VMDKs and attach those disks on the selected staging VM. The directories of the attached staging VM are then displayed. Select the files to be restored and click Restore.

      
10. On the File Restore page, you can choose one of the following restore targets.
    

    • Restore to CIFS share: Restores the files and folders to a specific network share.

      The restored file will be available on UNC share in the Phoenix-VMWare-FLR-[jobid] folder. 

      Field	Description
      UNC Path	Valid UNC share (network share) path that is reachable from the selected vCenter/ESXi. Valid sharename format: \\<hostname> or<Ip address>\<Sharename> //Host/Folder                        Note: UNC sharename must not have any Unicode characters.
      Username	Valid username of UNC share. Note: You can specify domain name in the username of the UNC share in the "domain@username" format.
      Password	Valid password for UNC share.
      Destination VMware Setup	From the drop-down list, select a vCenter/ESXi that has at least one backup proxy in the connected state.
      Backup Proxy Pool	From the drop-down list, select a backup proxy pool. It is recommended that you select a backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore.
      Staging VM	Select a staging VM with credentials assigned or credentials not assigned.  If you select a staging VM without credentials, then the Credentials field is displayed. Note: This field lists the staging VMs only if it follows all the prerequisites. Note: The staging VM is used to mount volumes for file-level restores to the target VM. Note: An administrator can assign credentials for the staging VM from All Virtual Machines page on the Management Console. For more information, see Manage credentials for VMware servers.
      Enter credentials for the selected staging VM
      Credentials	Select or enter credentials for the selected staging VM. If you click the Custom value, then you can create credentials and the Label, Username, and Password fields are displayed.
      Label	Enter a label for the staging VM.
      Username	Enter a valid username for the staging VM.
      Password	Enter a valid password for the staging VM.

    • Restore to Virtual Machine: Restores the files and folders to the original or specified VM.

      • Restore to original VM: Select this option if you want to restore the selected files to the same virtual machine.
         

        Field	Description
        Guest OS Credentials
        Username	Valid username.
        Password	Valid password.
        Location	Browse to the location where you want to restore files.
        Backup Proxy Pool	From the drop-down list, select a Backup proxy pool. It is recommended that you select a Backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore.
        Staging VM	Select a staging VM with credentials assigned or credentials not assigned.  If you select a staging VM without credentials, then the Credentials field is displayed. Note: This field lists the staging VMs only if it follows all the prerequisites. Note: The staging VM is used to mount volumes for file-level restores to the target VM. Note: This field is prepopulated by the same staging VM used in the previous flow to list the available files and folders. However, you can modify this.
        Enter credentials for the selected staging VM
        Credentials	Select or enter credentials for the selected staging VM. If you click the Custom value, then you can create credentials and the Label, Username, and Password fields are displayed.
        Label	Enter a label for the staging VM.
        Username	Enter a valid username for the staging VM.
        Password	Enter a valid password for the staging VM.
        If original file (s) exist
        Always overwrite	The files with the same name will always be overwritten at the destination regardless of the file version or date. By default, this option is always selected.
        Always skip	The files with the same name will not be restored to the destination. The number of files skipped will be displayed in the progress logs.
        Overwrite if original is older	The files with the same name will be overwritten only if the files are older than the version being restored.
        Restore and move original to .orig	If the file being restored already exists at the destination, the version being restored will be saved with the same filename. While the existing file will be renamed to filename.ext.orig. On subsequent restores, the existing file versions at the destination will be appended with an incremental number such as filename.ext.orig1, filename.ext.orig2, and so on.
        Preserve original directory structure	You can preserve the entire source location directory structure, that is tree path while restoring a file to an alternate location. An example of original directory structure: If you are restoring folder “B” from the source location  Volume1/A/B/C/D to  F:/. The restored file structure will be  F:/A/B/C/D.

      • Restore to an Alternate VM: Select this option if you want to restore the selected files to a different virtual machine.
         

        Field	Description
        Destination VMware Setup	Select the required vCenter/ESXi.
        Destination Hypervisor	Select the required Hypervisor.
        Destination VM	Select the required virtual machine where you want to restore the files. Note: The timestamp under the Destination VM  drop-down lists the last time the virtual machine listing page was refreshed.
        Backup Proxy Pool	From the drop-down list, select a backup proxy pool. It is recommended that you select a backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore. Note: If the virtual machine has a backup proxy pool mapped to it, the mapped backup proxy pool is selected by default.
        Guest OS Credentials
        Username	Valid username.
        Password	Valid password.
        Location	Browse to the location where you want to restore files.
        Staging VM	You can select a staging VM with credentials assigned or credentials not assigned.  If you select a staging VM without credentials, then the Credentials field is displayed. Note: This field lists the staging VMs only if it follows all the prerequisites. Note: The staging VM is used to mount volumes for file-level restores to the target VM. Note: This field is prepopulated by the same staging VM used in the previous flow to list the available files and folders. However, you can modify this.
        Enter credentials for the selected staging VM
        Credentials	Select or enter credentials for the selected staging VM. If you click the Custom value, then you can create credentials and the Label, Username, and Password fields are displayed.
        Label	Enter a label for the staging VM.
        Username	Enter a valid username for the staging VM.
        Password	Enter a valid password for the staging VM.
        If original file(s) exist
        Always overwrite	The files with the same name will always be overwritten at the destination regardless of the file version or date. By default, this option is always selected.
        Always skip	The files with the same name will not be restored to the destination. The number of files skipped will be displayed in the progress logs.
        Overwrite if original is older	The files with the same name will be overwritten only if the files are older than the version being restored.
        Restore and move original to .orig	If the file being restored already exists at the destination, the version being restored will be saved with the same filename. While the existing file will be renamed to filename.ext.orig. On subsequent restores, the existing file versions at the destination will be appended with an incremental number such as filename.ext.orig1, filename.ext.orig2, and so on.
        Preserve original directory structure	You can preserve the entire source location directory structure, which is tree path while restoring a file to an alternate location. An example of original directory structure: If you are restoring folder “B” from the source location  Volume1/A/B/C/D to  F:/. The restored file structure will be  F:/A/B/C/D.