User Tools

Site Tools


tsm:tsm_tdpvmware_pb

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tsm:tsm_tdpvmware_pb [2022/02/06 18:30]
manu [Test a proxy node]
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 =====
 +
 +**Note:** In either of these sections a path to free disk space will be needed for tracing. ​
 +
 +Tracing of VM operations can be extensive. If the operation you are tracing processes a number of VMs, determine if the behavior can be duplicated on a smaller subset so that data collection is not cumbersome.
 +
 +==== For operations which are initiated via the Web user interface ==== 
 +
 +  * Edit the dsmvddk.opt (in the BAclient folder). Change the following options to be 6:
 +
 +  vixDiskLib.transport.LogLevel = "​6"​
 +  vixDiskLib.nfc.LogLevel = "​6"​
 +
 +  * Edit the optfile used by the datamover(in the BAclient folder). Add the following:
 +
 +  traceflag tid pid enter exit general vm
 +  tracefile <Path with free disk space>/​datamvr.trace
 +
 +  * Edit the vmcliprofile (/​opt/​tivoli/​tsm/​tdpvmware/​common/​scripts):​
 +
 +  Change the VMCLI_TRACE value to YES
 +  Remove the # from in front of VE_TRACE_FILE and VE_TRACE_FLAGS
 +
 +  * Recreate the problem experienced
 +  * Reverse the changes made to prevent tracing from running
 +  * Gather the following for review:
 +
 +  <Path with free disk space>/​datamvr.trace
 +  Entire /​opt/​Tivoli/​tsm/​tdpvmware/​common/​logs folder
 +  Entire /​opt/​Tivoli/​tsm/​tdpvmware/​tsmcli folder
 +  dsmwebcl.log from BAclient folder
 +  datamover dsminfo.txt file 
 +
 +https://​www.ibm.com/​support/​pages/​collecting-data-ibm-spectrum-protect-virtual-environments-data-protection-vmware-linux#​generalgather
 +
 +
 +==== For operations which are initiated manually from the command line, or during scheduled events ==== 
 +
 +  * Edit the dsmvddk.opt(in the BAclient folder). Change the following options to be 6:
 +  vixDiskLib.transport.LogLevel = "​6"​
 +  vixDiskLib.nfc.LogLevel = "​6"​
 +  * Edit the optfile used by the datamover(in the BAclient folder). Add the following:
 +  traceflag tid pid enter exit general vm
 +  tracefile <Path with free disk space>/​datamvr.trace
 +  * Recreate the problem experienced
 +  * Reverse the changes made to prevent tracing from running
 +  * Gather the following for review:
 +  <Path with free disk space>/​datamvr.trace
 +  dsmwebcl.log from BAclient folder
 +  datamover dsminfo.txt file 
 +
 +
 +
 +===== Communication pb between datamover and Vcenter =====
  
 https://​www.ibm.com/​support/​pages/​known-issues-and-limitations-data-protection-vmware-v81#​Data%20Mover%20Common%20Issues%20and%20Limitations https://​www.ibm.com/​support/​pages/​known-issues-and-limitations-data-protection-vmware-v81#​Data%20Mover%20Common%20Issues%20and%20Limitations
 +
 +Can you provide the following data:
 +
 +  * Stop the Webserver service ​
 +
 +  * Edit log4j file to have "​logger.ve.level = ALL" is set in C:\Program Files\Tivoli\TSM\baclient\plugins\vcloudsuite\sdk\log4j.properties
 +
 +  * Restart the webserver service ​
 +
 +  * Reproduce the error in the plugin (taking a note with the time-fram on which this error is reproduced)
 +
 +  * Then collect:
 +
 +  Vcsplugin.log located in the Baclient directory ​
 +  VEprofile folder, path : C:​\IBM\SpectrumProtect\webserver\usr\servers\veProfile ​
 +  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)
  
 ===== Test a proxy node ===== ===== Test a proxy node =====
Line 515: 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 =====
  
 Enable tracing: Enable tracing:
Line 544: 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.1644168620.txt.gz · Last modified: 2022/02/06 18:30 by manu