Merge pull request #49706 from markgalioto/aug222018

updating restore files from VM backup article

Author: TrishaMc

articles/backup/backup-azure-restore-files-from-vm.md

@@ -7,7 +7,7 @@ manager: shivamg
 keywords: item level recovery; file recovery from Azure VM backup; restore files from Azure VM
 ms.service: backup
 ms.topic: conceptual
-ms.date: 12/20/2017
+ms.date: 8/22/2018
 ms.author: pullabhk
 ---
 # Recover files from Azure virtual machine backup
@@ -27,13 +27,17 @@ To restore files or folders from the recovery point, go to the virtual machine a
 
 2. In the virtual machine's menu, click **Backup** to open the Backup dashboard.
 
-    ![Open Recovery Services vault backup item](./media/backup-azure-restore-files-from-vm/open-vault-from-vm.png)
+    ![Open Recovery Services vault backup item](./media/backup-azure-restore-files-from-vm/open-vault-for-vm.png)
 
-3. In the Backup dashboard menu, click **File Recovery** to open its menu.
+3. In the Backup dashboard menu, click **File Recovery**.
+
+    ![File recovery button](./media/backup-azure-restore-files-from-vm/vm-backup-menu-file-recovery-button.png)
+
+    The **File Recovery** menu opens.
 
     ![File recovery menu](./media/backup-azure-restore-files-from-vm/file-recovery-blade.png)
 
-4. From the **Select recovery point** drop-down menu, select the recovery point that contains the files you want. By default, the latest recovery point is already selected.
+4. From the **Select recovery point** drop-down menu, select the recovery point that holds the files you want. By default, the latest recovery point is already selected.
 
 5. To download the software used to copy files from the recovery point, click **Download Executable** (for Windows Azure VM) or **Download Script** (for Linux Azure VM).
 
@@ -89,7 +93,7 @@ After identifying the files and copying them to a local storage location, remove
 
 ![Unmount disks](./media/backup-azure-restore-files-from-vm/unmount-disks3.png)
 
-Once the disks have been unmounted, you receive a message letting you know it was successful. It may take a few minutes for the connection to refresh so that you can remove the disks.
+Once the disks have been unmounted, you receive a message. It may take a few minutes for the connection to refresh so that you can remove the disks.
 
 In Linux, after the connection to the recovery point is severed, the OS doesn't remove the corresponding mount paths automatically. The mount paths exist as "orphan" volumes and they are visible but throw an error when you access/write the files. They can be manually removed. The script, when run, identifies any such volumes existing from any previous recovery points and cleans them up upon consent.
 
@@ -207,7 +211,7 @@ If you have problems while recovering files from the virtual machines, check the
 | Exe output: *Exception connecting to the target* |Script is not able to access the recovery point    | Check whether the machine fulfills the previous access requirements. |  
 | Exe output: *The target has already been logged in via an iSCSI session.* | The script was already executed on the same machine and the drives have been attached | The volumes of the recovery point have already been attached. They may NOT be mounted with the same drive letters of the original VM. Browse through all the available volumes in the file explorer for your file |
 | Exe output: *This script is invalid because the disks have been dismounted via portal/exceeded the 12-hr limit. Download a new script from the portal.* |    The disks have been dismounted from the portal or the 12-hr limit exceeded | This particular exe is now invalid and can’t be run. If you want to access the files of that recovery point-in-time, visit the portal for a new exe|
-| On the machine where the exe is run: The new volumes are not dismounted after the dismount button is clicked | The iSCSI initiator on the machine is not responding/refreshing its connection to the target and maintaining the cache |    Wait for some mins after the dismount button is pressed. If the new volumes are still not dismounted, please browse through all the volumes. This forces the initiator to refresh the connection and the volume is dismounted with an error message that the disk is not available|
+| On the machine where the exe is run: The new volumes are not dismounted after the dismount button is clicked | The iSCSI initiator on the machine is not responding/refreshing its connection to the target and maintaining the cache. |  After clicking **Dismount**, wait a few minutes. If the new volumes are not dismounted, browse through all volumes. Browsing all volumes forces the initiator to refresh the connection, and the volume is dismounted with an error message that the disk is not available.|
 | Exe output: Script is run successfully but “New volumes attached” is not displayed on the script output |    This is a transient error    | The volumes would have been already attached. Open Explorer to browse. If you are using the same machine for running scripts every time, consider restarting the machine and the list should be displayed in the subsequent exe runs. |
 | Linux specific: Not able to view the desired volumes | The OS of the machine where the script is run may not recognize the underlying filesystem of the protected VM | Check whether the recovery point is crash consistent or file-consistent. If file consistent, run the script on another machine whose OS recognizes the protected VM's filesystem |
 | Windows specific: Not able to view the desired volumes | The disks may have been attached but the volumes were not configured | From the disk management screen, identify the additional disks related to the recovery point. If any of these disks are in offline state try making them online by right-clicking on the disk and click 'Online'|