APAR status
Closed as program error.
Error description
The file-level restore User Interface (FLR UI) displays the mounted file systems of the guest as expected but attempting to browse stops with the message : "An error occurred while retrieving the directory information. If the problem persists, contact your administrator." This will be seen when affected Linux guests uses the word 'root' in its Logical Volume Manager (LVM) Volume Group (VG) name. For example the fstab file would contain : # /etc/fstab /dev/mapper/rootvg-root / ext4 defaults 1 1 /dev/mapper/rootvg-home /home ext4 defaults 1 2 /dev/mapper/rootvg-opt /opt ext4 defaults 1 2 /dev/mapper/rootvg-tmp /tmp The following messages will be found in the product logs : a. In C:\IBM\SpectrumProtect\webser ver\usr\servers\veProfile\logs\fr_gui.log : <timestamp> MSK [tid=xx] [INFO] BaseCmdsProcessor - Response received->HttpRespo nse [result={"queryPath":"\/tsmmount\/file_restore\/vm_gues_name \/time-frame\/Volumex", "statusRC":115, "showSupportInfo":true, "statusMessage":"An error occurred while retrieving the directory information. If the problem persists, contact your administrator."}, returnCode=200, command =VeFr/DirEntries] <timestamp>... MSK [tid=xx] [ERROR] java.lang.reflect.InvocationTargetException at .. Caused by: com.ibm.flr.command.FlrCmdException: Unsuccessful return code at .. b. In a 'VM' trace of the Linux mount proxy node : Here we see the guest LVM VG names query output : <timestamp> [PID] [TID]: FileLevelRestore/Utils.cpp( 462): executeCommand: Full command string: timeout 120 lvm pvs -o pv_name,vg_name --noheadings <timestamp> [PID] [TID] : FileLevelRestore/Utils.cpp( 482): executeCommand: Command Output: /dev/sda2 rootvg /dev/sdb2 rootvg /dev/sdc datavg and here an example of the duplicate file system name '/home' which causes the FLR UI problem : <timestamp>: FileLevelRestore/Linu xFunctions.cpp(xx): FindOriginalMountpoints: 2: '/dev/mapper/vg_tsmvesnap_sdb2-home','ext4','home','uuid' .. This device is a TSM snapshot LVM ..A matching LVM name 'home' is present in FSTAB. ..==> FOUND original Mount point '/home' for Volume '/tsmmount/file_restore/vm_name/xxx/Volume2'! ..4: '/dev/mapper/vg_tsmvesnap_sdb2-root','ext4','root','uuid' ..This device is a TSM snapshot LVM ..A matching LVM name 'root' is present in FSTAB. ..==> FOUND original Mount point '/home' for Volume '/tsmmount/file_restore/vm_name/xxx/Volume4'! <timestamp>: FileL evelRestore/LinuxFunctions.cpp(xx): FindOriginalMountpoints: Original mountpoints of mounted volumes: .. ---------------------------------------- .. MountDir OriginalMountPoint DeviceName FileSystemType MountStatus .. 1: /tsmmount/file_restore/vm_name/xxx/Volume1 /boot /dev/sdb1', ext4 mounted .. 2: /tsmmount/file_restore/vm_name/xxx/Volume2 /home /dev/mapper/vg_tsmvesnap_sdb2-home ext4 mounted ... .. 4: /tsmmount/file_restore/vm_name/xxx/Volume4 /home /dev/mapper/vg_tsmvesnap_sdb2-root ext4 mounted .. 5: /tsmmount/file_restore/vm_name/xxx/Volume5 /tmp /dev/mapper/vg_tsmvesnap_sdb2-tmp ext4 mounted ... The original mount point search algorithm is mixing the LVM name "root" with the VG name "rootvg". IBM Spectrum Protect Versions Affected: IBM Spectrum Protect for Virtual Environments - Data Protection for VMware 7.1 and 8.1 on Windows. IBM Spectrum Protect for Virtual Environments - Data Protection for VMware 8.1.4 and newer on Windows. Initial Impact: Medium
Local fix
1. Avoid naming LVM VG with 'root'. OR: 2. If renaming is not immediately possible : - mount the needed Linux guest file system individually using the native Recovery Agent GU
Problem summary
**************************************************************** * USERS AFFECTED: * * Data Protection for VMware Data Mover version 7.1 and 8.1 * * running on Microsoft Windows x64 and Linux x86 platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * This issue is projected to be fixed in the Data Protection * * for VMware Data Mover version 8.1.11 on all Microsoft * * Windows x64 and Linux x86 platforms * * * * Note 1: This is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
While searching for an original mount points of LVM volumes the Data Mover compares the LV names with the records found in /etc/fstab of the Guest VM. This comparison was done with simple search function and was ambiguous. Due to this a volume could sometimes be mapped to wrong partition and therefore can not be mounted. The search algorithm has been improved to eliminate such cases.
Temporary fix
Comments
APAR Information
APAR number
IT33947
Reported component name
TSM FOR VE DP V
Reported component ID
5725TVEVM
Reported release
81W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-08-19
Closed date
2020-09-18
Last modified date
2020-09-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
dsmcad
Fix information
Fixed component name
TSM FOR VE DP V
Fixed component ID
5725TVEVM
Applicable component levels
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS8TDQ","label":"Tivoli Storage Manager for Virtual Environments"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81W"}]
Document Information
Modified date:
13 February 2021