IT36934: BACKUPS OF VIRTUAL MACHINES CAN FAIL WITH ANS4174E RC=2070 AFTER UPGRADING TO 8.1.11.

APAR status

• Closed as program error.

Error description

• IBM Spectrum Protect for Virtual Environments - Data Protection
  for VMware  8.1.11 backups can fail with the following messages
  seen in the data mover node error log:
  
  ANS0246E Issue dsmEndTxn and then begin a new transaction
  session.
  ANS0361I DIAG: ..\..\common\vm\vmbackcommon.cpp(3595):
  VmBackupControlFiles(): Error 2070 sending
  ANS4174E Full VM backup of VMware Virtual Machine failed with
  RC=2070 mode=Incremental Forever - Incremental, target node
  name=? DC_node_name?, data mover node name=?DM_node_name?
  ANS1228E Sending of object failed.
  ANS0246E Issue dsmEndTxn and then begin a new transaction
  session.
  ANS0246E Issue dsmEndTxn and then begin a new transaction
  session.
  ANS0361I DIAG: ..\..\common\vm\vmbackcommon.cpp(3595):
  VmBackupControlFiles(): Error 2070 sending
  ANS4174E Full VM backup of VMware Virtual Machine failed with
  RC=2070 mode=Incremental Forever - Incremental, target node
  name=? DC_node_name?, data mover node name=?DM_node_name?
  ANS1228E Sending of object failed.
  ANS0246E Issue dsmEndTxn and then begin a new transaction
  session.
  | MDVREGR 8.1.11-TIV_5725TVEVM |
  
  IBM Spectrum Protect Versions Affected:
  IBM Spectrum Protect for Virtual Environments - Data Protection
  for VMware version 8.1.11.0 on Windows and Linux
  
  Initial Impact: Medium
  
  Additional Keywords: TSM, Tivoli, Storage, Manager, TS005053048,
  Spectrum Protect, TDP4VE .
  

Local fix

• The local fix consists of several steps, depending on the
  current configured options. The backup will fail when either the
  TXNBytelimit or the TXNGroupmax limit is reached.
  
  1. Verify no TXNBytelimit is set for the datamover. Remove the
  option from the datamover dsm.opt and verify if the backups are
  working now. If the backup still fails, continue with step 2
  2.Query the DC node from the server side, to know the used
  TXNGroupmax value.
  3. Increase TXNGroupmax on the for the used DC node to a higher
  value, e.g. 6144
    update node <datacenter node name>  TXNGroupmax=6144
     Verify if the backup is working now. If still failing,
  continue with step 4.
  4. Increase TXNGroupmax with increments of 2048 until the backup
  is working.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect for Virtual Environments Data           *
  * Protection for VMware versions 8.1.11 and 8.1.12 running on  *
  * all 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.13 on Windows x64 and      *
  * Linux x86 platforms.                                         *
  * Note 1: This is subject to change at the discretion of IBM.  *
  ****************************************************************
  

Problem conclusion

• Txn limits are now correctly checked when sending control files.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• dsmagent
  

Fix information

• Fixed component name

  TSM FOR VE DP V

• Fixed component ID

  5725TVEVM

Applicable component levels