tsm:tsm_tdpvmware_pb
Differences
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 [2022/09/08 23:04] manu |
tsm:tsm_tdpvmware_pb [2024/03/22 13:47] (current) manu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Errors on TDP for VE ====== | ====== Errors on TDP for VE ====== | ||
| + | |||
| + | ===== Restore a VM in thin_provisionning ===== | ||
| + | |||
| + | Use the follwin flag in your command | ||
| + | <code> | ||
| + | -testflag=VMRESTOR_DONT_FORCE_THICK | ||
| + | </code> | ||
| ===== Main tracing for VE backups ===== | ===== Main tracing for VE backups ===== | ||
| Line 72: | Line 79: | ||
| Vcsplugin.log located in the Baclient directory | Vcsplugin.log located in the Baclient directory | ||
| VEprofile folder, path : C:\IBM\SpectrumProtect\webserver\usr\servers\veProfile | VEprofile folder, path : C:\IBM\SpectrumProtect\webserver\usr\servers\veProfile | ||
| - | Screenshot for all the plugin tabs the vCenter host the following : | + | Screenshot for all the plugin tabs the vCenter host the following : /storage/vsphere-ui/IBMDataProtection/logs/log.txt (this exactly our log-Discussion between our plugin and webserver) |
| - | /storage/vsphere-ui/IBMDataProtection/logs/log.txt (this exactly our log-Discussion between our plugin and webserver) | + | |
| ===== Test a proxy node ===== | ===== Test a proxy node ===== | ||
| Line 585: | 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 614: | 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 2 ===== | ||
| + | |||
| + | VM BACKUPS CAN FAIL WITH ANS4174E & ANS1907E | ||
| + | |||
| + | Virtual machine backups can fail with the following error even | ||
| + | when using "testflag GLTEMPNAMECLEANUP". | ||
| + | |||
| + | ANS4174E Full VM backup of VMware Virtual Machine | ||
| + | 'virtual machine name' failed with RC=45 mode=Incremental Forever - Incremental, | ||
| + | target node name='IBM', data mover node name='IBM_DM' | ||
| + | |||
| + | Add the option into dsm.sys on linux or dsm.opt on a windows datamover | ||
| + | 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> | ||
tsm/tsm_tdpvmware_pb.1662671083.txt.gz · Last modified: 2022/09/08 23:04 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
