what is the LVM version it it LVM2?

have a look at the supported file system for Vmware policy type in below 7.x Virtual Doc page No 25

, http://www.symantec.com/business/support/index?page=content&id=TECH127089

if the file systems are not supported by Vmware policy , you need to recover the entire VM to retrive the data inside these file systesm. 

individual file and folder restore is not possible from the file systems that are not supported.. but data can be recovered though Full VM recovery.

 LVM version:     2.02.111(2)-RHEL6 (2014-09-01)
  Library version: 1.02.89-RHEL6 (2014-09-01)
 

I can see data of those lvm mount points in restore panel under /etc/LVM/Profiles.. but pain area is why I am not able to see these lvm mount points directly as /home , /opt , /usr etc.. why eerything is under /etc/LVM/Profile hierarchy

Curious to see output of 'df -h' on this client.

Any possibility that these volumes are RDM or 'independent disks'?

output of df -h is attached.. these are not independent & RDM disks.

Is there any possiblity, any data of lvm on RDM can be backed up under /etc/LVM disk ?

Hi Mnolan

I cheked /etc/lvm/lvm.conf file, it is as follows :

# To put this file in a different directory and override /etc/lvm set
# the environment variable LVM_SYSTEM_DIR before running the tools.
    # Directory where LVM looks for configuration profiles.
    profile_dir = "/etc/lvm/profile"
    dir = "/dev"
    # An array of directories that contain the device nodes you wish
    # subdirectories found in the device directory. This setting is applied
    # to udev-managed device directory only, other directories will be scanned
    # udev directory will be ignored with this setting on.
    # If several entries in the scanned directories correspond to the
    # By default this cache is stored in the /etc/lvm/cache directory
    cache_dir = "/etc/lvm/cache"
 

so I believe your first tech note has solved the mystery, I will update the backup host and then check the next backup & will share the result.

Did it fix the issue?

Which version did you update to, because I cannot find any reference that this etrack was fixed in 7.6.0.4 :-)

The Etrack referenced in TECH222609 is resolved in 7.6.0.4 (3553489) and was scheduled to be resolved in 7.6.1.1 (3575310).

Thanks Chris!