How to restore individual files when FLR fails

KB ID: 1459
Product: Veeam Backup & Replication | 10 | 11
Published: 2011-12-20
Last Modified: 2022-03-15
Languages: FR
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents an alternate method to restore individual files when either the File Level Restore fails or the filesystem is not compatible with the Guest OS File Recovery functionality of Veeam Backup & Replication.

If the data you are trying to restore is located on a single disk, a simpler alternative is to perform Instant Disk Recovery using an unoccupied SCSI node. This will allow you to temporarily attach a restored copy of the disk to the VM and copy the required files. When complete, you then unmount on the Instant Recovered disk.

Solution

This restore method is the virtual equivalent of plugging a USB drive into one machine, copying the files needed to the drive, and then taking that drive to another machine. In this case, we are creating a new temporary virtual disk, attaching it to the Instant Recovered VM, copying the needed files to the disk, and then disconnecting and reconnecting that VMDK to the production machine.
Critical Details

When initiating the Instant Recovery, you must

Restore Process

  1. Launch an Instant Recovery of the Virtual Machine you need to retrieve files from.
    • Use the “Restore to a new location” option.
      Failure to select this will cause the Instant Recovery to prompt asking if the production machine should be deleted.
    • You must rename the Virtual Machine when performing the Instant Recovery. It is suggested to add a suffix, such as "_ir" or "_restored"
      Failure to rename the Instant Recovered VM will cause the Instatnt Recovery wizard to prompt asking to overwrite the production server.
    • Uncheck the box for "Connect VM to network."
      Failure to do so will cause the restored VM to communicate with the production network and cause an IP conflict.
  2. After the Instant Recovery is successfully published, in VMware vSphere Client, create a new virtual disk for the VM. Create the disk on a production datastore. Make the disk large enough to contain the files you need to retrieve.
Add new disk
set size and location
Make the disk large enough to hold the data you plan to copy out of the VM, and create the disk on a production datastore.
  1. Connect to the Guest OS of the Instant Recovered VM. As the VM has no network connection, you will need to use local credentials or cached credentials.
  2. Initialize and format the additional disk like any other disk in that operating system.
  3. Transfer the data you want to restore to that disk.
  4. When all data you need to retrieve is on the extra VMDK, edit the Instant Recovered VM and note the disk's name and location. Then, remove the extra disk from the instant recovered VM.
Note location and disconnect
  1. Attach the extra disk to the machine in Production where the files are needed.
Add existing disk
  1. Copy the files off the extra disk.

Cleanup

After the files have been copied off the extra disk, perform the following steps to clean up the environment:

  1. Remove the extra disk that was attached to the Production VM.
    You may choose to delete the disk from the datastore.
  2. Stop Publishing the Instant Recovery
Stop publishing

More Information

  • This method can be used to restore files from any file system, which helps bypass the limitations of Windows FLR and multi-OS FLR.
  • Instant Recovery can usually be accomplished in minutes, but recovery of large VMs from deduplicating storage may take over an hour.
  • Instant Recovery to VMware does not require pre-allocating datastore space for the disk of the Instant Recovered VM. 
  • Instant Recovery for Hyper-V will pre-allocate the entire size of the virtual disks.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.