NVP vProxy: Il ripristino FLR ha esito negativo con: Impossibile importare oggetti LVM

Summary: Il ripristino FLR ha esito negativo con: Impossibile importare oggetti LVM Il disco deve essere aggiunto a un gruppo di volumi (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

Durante un ripristino a livello di file (FLR) NetWorker VMware Protection (NVP) con l'appliance vProxy, il processo di montaggio FLR non riesce e si registra il seguente errore nel log di montaggio:
  
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.  


Luoghi:

Server NetWorker:

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

L'attuale layout del disco della VM (LVM) mostra che il PV {/dev/sde1} non fa parte di 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

In base a NetWorker VMware Integration Guide, FLR presenta le seguenti limitazioni LVM:
  • Thin provisioning di LVM (Logical Volume Management)
  • LVM con qualsiasi volume fisico (PV) non allocato a un gruppo di volumi (VG)
Per questi backup è supportato solo il ripristino dell'immagine.

Anche se la configurazione LVM viene corretta in modo che il PV sia allocato a un VG, non è possibile eseguire FLR dei backup esistenti.
I backup vengono eseguiti dopo l'allocazione del PV LVM a un VG che supporta FLR; solo se LVM non utilizza il thin provisioning.

Additional Information

Vedere la sezione FLR Limitations della NetWorker VMware Integration Guide. La documentazione di NetWorker è disponibile tramite: https://www.dell.com/support/home/product-support/product/networker/docs

NVP vProxy: Limitazioni di FLR LVM

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.