This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tsm:tsm_tdpvmware_pb [2023/12/21 13:44] manu |
tsm:tsm_tdpvmware_pb [2024/03/22 13:47] (current) manu |
||
---|---|---|---|
Line 4: | Line 4: | ||
Use the follwin flag in your command | Use the follwin flag in your command | ||
- | -testflag=VMRESTOR_DONT_FORCE_THICK | + | <code> |
+ | -testflag=VMRESTOR_DONT_FORCE_THICK | ||
+ | </code> | ||
===== Main tracing for VE backups ===== | ===== Main tracing for VE backups ===== | ||
Line 590: | Line 591: | ||
Right-click the VMware Tools Service and click Restart. | Right-click the VMware Tools Service and click Restart. | ||
| | ||
- | ===== Trace TDP VE ===== | + | ===== Trace TDP VE 1 ===== |
Enable tracing: | Enable tracing: | ||
Line 619: | Line 620: | ||
The command will generate the dsminfo.txt and dsmmsinfo.txt files. | The command will generate the dsminfo.txt and dsmmsinfo.txt files. | ||
- | ===== Trace TDP VE ===== | + | ===== Trace TDP VE 2 ===== |
VM BACKUPS CAN FAIL WITH ANS4174E & ANS1907E | VM BACKUPS CAN FAIL WITH ANS4174E & ANS1907E | ||
Line 632: | Line 633: | ||
Add the option into dsm.sys on linux or dsm.opt on a windows datamover | Add the option into dsm.sys on linux or dsm.opt on a windows datamover | ||
testflag GLTEMPNAMECLEANUP | testflag GLTEMPNAMECLEANUP | ||
+ | | ||
+ | ===== Trace TDP VE 3 ===== | ||
+ | |||
+ | To solve the path library issue, please apply the following steps: | ||
+ | |||
+ | 1. Use the IBM-installed Java version, located at the Linux installation location for Java: export JAVA_HOME=/opt | ||
+ | <code> | ||
+ | /tivoli/tsm/tdpvmware/common/jre/jre | ||
+ | </code> | ||
+ | |||
+ | 2.Set the relevant environment variables. | ||
+ | |||
+ | a. Ensure that the JAVA_HOME environment variable is exported correctly: | ||
+ | <code> | ||
+ | JAVA_HOME=<jre-or-jdk-install-dir> | ||
+ | </code> | ||
+ | |||
+ | b. Ensure that the PATH environment variable is exported correctly: | ||
+ | <code> | ||
+ | export PATH=$PATH:$JAVA_HOME/jre/bin | ||
+ | </code> | ||
+ | |||
+ | 3.Then trace the backup, with the following steps: (The above Java failure is not related to Jackson files) | ||
+ | |||
+ | A-Enable the Vcsplugin tracing: | ||
+ | |||
+ | 1.Edit the log4j.properties located in "/opt/tivoli/tsm/client/ba/bin/plugins/vcloudsuite/sdk/log4j.properties" with the following options: | ||
+ | <code> | ||
+ | logger.ve.level = TRACE | ||
+ | rootLogger.level =TRACE | ||
+ | </code> | ||
+ | |||
+ | B.Enable tracing for the backup: | ||
+ | |||
+ | 1. Enable VDDK debug log level by editing in file C:\Program Files\Common Files\Tivoli\TSM\IBMVDDK\dsmvddk.opt to have : | ||
+ | <code> | ||
+ | vixDiskLib.transport.LogLevel = "6" | ||
+ | vixDiskLib.nfc.LogLevel = "6" | ||
+ | </code> | ||
+ | |||
+ | 2. Run the backup VM command with tracing options: | ||
+ | <code> | ||
+ | dsmc backup VM <vmname>–optfile=<datamover optfile name> -tracefile=c:\test_vm.trc -traceflags=service,vm > c:\test_vm.out | ||
+ | |||
+ | dsmc show VM all –optfile=<datamover optfile name> -tracefile=c:\show_vm.trc -traceflags=service,vm > c:\show_vm.out | ||
+ | </code> | ||
+ | |||
+ | 3. Generate a new dsminfo.txt for the data mover node | ||
+ | |||
+ | >> by running this command from the BAclient installation directory: | ||
+ | <code> | ||
+ | dsmc query systeminfo –optfile=<datamover optfile name> - Generates the ‘dsminfo.txt’ file | ||
+ | </code> | ||
+ | |||
+ | 4. Please send : | ||
+ | <code> | ||
+ | dsminfo.txt | ||
+ | c:\test_vm.out | ||
+ | test_vm.trc | ||
+ | </code> | ||
+ | |||
+ | d.Vcsplugin.log located in "/opt/tivoli/tsm/client/ba/bin/" | ||
+ | <code> | ||
+ | c:\show_vm.out | ||
+ | c:\show_vm.tr | ||
+ | </code> |