IT09781: AFTER UPGRADE TO A 6.4.3 OR 7.1.2 TSM LINUX X86 CLIENT DATAMOVER FROM 6.4.0.0, VMWARE INCREMENTAL BACKUPS ON RH 5.9 FAIL

APAR status

• Closed as Permanent restriction.

Error description

• If a 6.4.0.0 IBM Tivoli Storage Manaer (TSM) Backup-Archive
  (B/A) Linux x86 client is used as a datamover for incremental
  VMware backups with the 6.4 TSM for Virtual Environments (TSM
  for VE): Data Protection for VMware product on RedHat 5.9, and
  then the client is upgraded to 6.4.3 or 7.1.2, subsequent
  incremental VMware backups fail.
  
  This issue does not occur on RHEL 6 and does not occur upgrading
  from TSM 6.4.0.0 to 6.4.1, 6.4.2, 7.1.0, or 7.1.1. The issue
  also does not occur when upgrading from a datamover level
  between 6.4.0.1 and 6.4.2.
  

Local fix

• From 6.4.0.0, first upgrade to a TSM 6.4.0.x, 6.4.1, or 6.4.2
  Linux x86 B/A client for the datamover (where x >=1) and then
  upgrade to 6.4.3, or first upgrade to a TSM 7.1.0 or 7.1.1 Linux
  x86 B/A client, and then upgrade to 7.1.2.y.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager for Virtual Environments version      *
  * 6.4.0 running on Linux 5.9 and 5.11 x86_64 platforms.        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Tivoli Storage Manager for Virtual Environments version      *
  * 6.4.0 running on Linux 5.9 and 5.11 x86_64 platforms should  *
  * be upgraded to Tivoli Storage Manager for Virtual            *
  * Environments version 6.4.1 before upgrading to other         *
  * version.                                                     *
  ****************************************************************
  

Problem conclusion

• Close it as a permanent restriction.
  

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

• dsmc
  

Fix information

Applicable component levels