dcz01
ADSM.ORG Senior Member
Hello,
I hope someone could help me here.
I'm now searching a lot of time for an solution of my error with the TSM client and the ReaR tool that says always that one important library of the client is missing.
Does someone know the client library "libvixDiskLib.so.6"?
ReaR is an Deaster Recovery tool which workes normally great with TSM:
Here is the old problem which i had a time ago:
And here is the actual output of the ReaR tool in an CentOS 8.2 with TSM client 7.1.8.9 and ReaR version 2.6:
Could it be that problem?
Greetings
dcz01
I hope someone could help me here.
I'm now searching a lot of time for an solution of my error with the TSM client and the ReaR tool that says always that one important library of the client is missing.
Does someone know the client library "libvixDiskLib.so.6"?
ReaR is an Deaster Recovery tool which workes normally great with TSM:
Relax-and-Recover - Linux Disaster Recovery
relax-and-recover.org
GitHub - rear/rear: Relax-and-Recover - Linux bare metal disaster recovery and system migration solution (cfr. mksysb, ignite)
Relax-and-Recover - Linux bare metal disaster recovery and system migration solution (cfr. mksysb, ignite) - rear/rear
github.com
Here is the old problem which i had a time ago:
ERROR: ReaR recovery system not usable (missing libraries for TSM libraries) · Issue #1533 · rear/rear
ERROR: ReaR recovery system not usable (TSM) Fill in the following items before submitting a new issue (quick response is not guaranteed with free support): rear version (/usr/sbin/rear -V): Relax-...
github.com
And here is the actual output of the ReaR tool in an CentOS 8.2 with TSM client 7.1.8.9 and ReaR version 2.6:
Code:
[root@FBD01PSS ~]# rear mkrescue
Broken symlink '/etc/grub2.cfg' in recovery system because 'readlink' cannot determine its link target
Broken symlink '/usr/lib/modules/4.18.0-193.28.1.el8_2.x86_64/build' in recovery system because 'readlink' cannot determine its link target
Broken symlink '/usr/lib/modules/4.18.0-193.28.1.el8_2.x86_64/source' in recovery system because 'readlink' cannot determine its link target
There are binaries or libraries in the ReaR recovery system that need additional libraries /bin/gdisk requires additional libraries (fatal error)
/opt/tivoli/tsm/client/ba/bin/libvixMntapi.so.1.1.0 requires additional libraries (specified as non-fatal)
libvixDiskLib.so.6 => not found
ReaR recovery system in '/tmp/rear.pa35lFzY1gbEn8m/rootfs' needs additional libraries, check /var/log/rear/rear-FBD01PSS.log for details
Build area kept for investigation in /tmp/rear.pa35lFzY1gbEn8m, remove it when not needed
ERROR: ReaR recovery system in '/tmp/rear.pa35lFzY1gbEn8m/rootfs' not usable (required libraries are missing)
Some latest log messages since the last called script 990_verify_rootfs.sh:
partprobe is /bin/partprobe
wipefs is /bin/wipefs
mkfs is /bin/mkfs
mkfs.vfat is /bin/mkfs.vfat
mkfs.xfs is /bin/mkfs.xfs
xfs_admin is /bin/xfs_admin
mkswap is /bin/mkswap
ldconfig is /bin/ldconfig
Aborting due to an error, check /var/log/rear/rear-FBD01PSS.log for details
Beendet
Could it be that problem?
1831969 – vddk: vddk7.0 not supported
bugzilla.redhat.com
Source:Troubleshooting VMware - SEPsesam
wiki.sep.de
Greetings
dcz01