Before you perform KVM recovery, review the following considerations and limitations:

• You can only recover to a storage pool that NetBackup has discovered. If no storage pools have been discovered, you must first create a storage pool and then run discovery to discover that storage pool.

• Full VM recovery is supported with both full and incremental backups.

• If a VM disk did not reside in a storage pool at time of backup, the recovery option Restore to the original location is not available.

• NetBackup supports backup of Linux FIFO files on KVM guests. However, NetBackup does not support restoring FIFO files individually through KVM Single File Restore (SFR). FIFO files are restored when you recover the entire virtual machine.

  A granular or KVM SFR job may fail or may not create the named pipe on the destination. For example, destination nbtar reports status 185. The tar did not find all the files to be restored, or the restore completes without the FIFO being present, even though the object appears in browse/selection.

  SFR builds a tar stream. FIFOs are special files and the path from Catalog > stream > nbtar can omit or mishandle the FIFO. This is a known limitation and not a supported granular use case for FIFOs.

  To resolve the issue, FIFO files should be restored when KVM full VM recovery is performed.

• Downloading of files and folders with SFR is not supported for accelerator-disabled incremental backup images.

• Raw disks are not mapped for file boundaries and are not supported with SFR.