Files are selected from multiple drives (volumes) on the virtual machine.

For example: The original virtual machine had two drives (C:\ and D:\), and files from each drive are selected in the same restore operation. Messages similar to the following appear in the job progress log:

13:26:05 (86.001) (86.001) INF - Skipping to next file header...
13:26:05 (86.001) (86.001) INF - TAR EXITING WITH STATUS = 0
13:26:05 (86.001) (86.001) INF - TAR RESTORED 11368 OF 11463 FILES
 SUCCESSFULLY
13:26:05 (86.001) (86.001) INF - TAR KEPT 0 EXISTING FILES
13:26:05 (86.001) (86.001) INF - TAR PARTIALLY RESTORED 0 FILES

13:26:15 (86.001) Status of restore from image created 7/21/2008 
2:55:05 PM = the requested operation was partially successful

Select files from a single drive at a time. Selecting files from multiple drives is not supported.

You have attempted to restore the files into a mapped drive on the virtual machine. The restore fails with NetBackup status code 185.

Restore the files by means of a shared location on the virtual machine (with a UNC path) rather than by means of a mapped drive.

See Restoring individual Hyper-V files to a shared location on the virtual machine.

The snapshot contains invalid inodes.

Windows Hyper-V provides no mechanism for quiescing file system activity on Linux virtual machines. As a result, invalid inodes may be present in the snapshot. A backup that was made with the Enable file recovery from VM backup option may have file-mapping failures if the virtual machine experiences heavy I/O. The failures are reported in the NetBackup Administration Console in this form:

ERR - Unable to read metadata for index: 379023, VFM error = 6.

Note that the backup succeeds, but any files with metadata errors cannot be restored individually.

For the backups that enable individual restore of all files, schedule the backup when the I/O activity is lower. If metadata errors persist, shut down the virtual machine during the backup.