NVP vProxy: FLR recovery fails with: Unable to import LVM objects

Summary: FLR recovery fails with: Unable to import LVM objects Disk must be added to a volume group (VG)

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

During a NetWorker VMware Protection (NVP) File Level Restore (FLR) with the vProxy appliance, the FLR mount process fails, logging the following error in the mount log:
  
FLR-vproxy-1-57268d3e-9517-4f68-845a-fddfeaf5425a_5 /dev/loop3p1]): exit status 8
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:00Z NOTICE: [@(#) Build number: 168] DD Host = 'dd-name', DD Model = 'DD####', DDOS Version = 'Data Domain OS #.#.#.##-#####', DDBoost Version = '#.#.#.#-######'
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:00Z INFO: [@(#) Build number: 168] Releasing datastore 'EMC-FLR-vproxy-1-1571838298' (datastore-name)
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:00Z INFO: [@(#) Build number: 168] Deleting temporary datastore 'EMC-FLR-vproxy-1-1571838298' (datastore-name)
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:07Z INFO: [@(#) Build number: 168] Removing NFS export at 'dd-name:/data/col1/nsr-mtree/FLR-vproxy-1-57268d3e-9517-4f68-845a-fddfeaf5425a'
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:10Z INFO: [@(#) Build number: 168] Destroying cloned backup images
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:12Z INFO: [@(#) Build number: 168] Unlocking VM
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:12Z INFO: [@(#) Build number: 168] Found virtual machine 'vm-name' with MORef 'vm-number'.
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:13Z INFO: [@(#) Build number: 168] Set custom attribute 'EMC vProxy FLR Session' value for object vm-number to ''.
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:13Z INFO: [@(#) Build number: 168] Unlocked virtual machine.
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:13Z INFO: [@(#) Build number: 168] Disconnected from session on vCenter 'vCenter-name'.
159373:nsrvproxy_flr: vProxy Log: 2019-10-25T08:06:13Z ERROR: [@(#) Build number: 168] Unable to import LVM objects ([-i -n FLR-vproxy-1-57268d3e-9517-4f68-845a-fddfeaf5425a_5 /dev/loop3p1]): exit status 8
152793:nsrvproxy_flr: vProxy Log Ends =================================================
150017:nsrvproxy_flr: Saveset Mount was terminated...

164881:nsrvproxy_flr: Operation completed with errors.  


Locations:

NetWorker server:

Linux: /nsr/logs/adhoc/nsrvproxy_flr/######.log
Windows: C:\Program Files\EMC NetWorker\nsr\logs\adhoc\nsrvproxy_fler\######.log

vProxy: /opt/emc/vproxy/runtime/logs/recycle/vflrd/YYYYMMDD_1/mount-######.log

Cause

The current VM disk layout (LVM) shows that PV {/dev/sde1} is not part of VG.

###################################################
# Command used to generate this file: pvs -v
# Output Filename: pvs_-v.txt
###################################################

  PV         VG                         Fmt  Attr  PSize       PFree   DevSize PV UUID
  /dev/sda2  vg_root                    lvm2 a--u  19.51g      0       19.51g  <removed>
  /dev/sdb1  vg99_content               lvm2 a--u  2.00t       0       2.00t   <removed>
  /dev/sdc1  vg99_apps                  lvm2 a--u  200.00g     100.00g 200.00g <removed>
  /dev/sdd1  vg99_apache                lvm2 a--u  4.99g       0       4.99g   <removed>
  /dev/sde1                             lvm2 ----  50.00g      50.00g  50.00g  <removed>
  /dev/sdf1  vg99_content_del           lvm2 a--u  50.00g      0       50.00g  <removed>
  /dev/sdg1  vg99_index                 lvm2 a--u  50.00g      0       50.00g  <removed>

Resolution

As per the NetWorker VMware Integration Guide, FLR has the following LVM limitations:
  • Logical Volume Management (LVM) thin provisioning
  • LVM having any Physical Volume (PV) not allocated to a Volume Group (VG)
Only Image Restore is supported for these backups.

Even if the LVM configuration is corrected so that the PV is allocated to a VG, it is not possible to perform FLR of existing backups.
Backups are performed after the LVM PV is allocated to a VG supports FLR; only if the LVM is not using thin provisioning.

Additional Information

See FLR Limitations section of the NetWorker VMware Integration Guide. NetWorker documentation is available through: https://www.dell.com/support/home/product-support/product/networker/docs

NVP vProxy: FLR LVM Limitations

Affected Products

NetWorker

Products

NetWorker
Article Properties
Article Number: 000048007
Article Type: Solution
Last Modified: 06 Feb 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.