IT39410: MINIMAL REBALANCING OF VMWARE VIRTUAL MACHINES OVER DATA MOVERS DOES NOT WORK AS EXPECTED

APAR status

• Closed as program error.

Error description

• After an initial tagging-compatible scheduled backup of one
  
  VMware virtual machine (VM), the VM is not assigned to the
  default data mover by IBM Spectrum Protect for Virtual
  Environments: Data Protection for VMware.
  
  Messages like the following are logged in the scheduler log at
  the end of the scheduled backup:
  
  [date] [time] Total number of virtual machines processed: 1
  [date] [time] ANS4313I Rebalance Schedule SCHEDULE_NAME Type:
                Minimal
  [date] [time] No virtual machines are assigned to the default
                data mover.
  [date] [time] Scheduled event 'SCHEDULE_NAME' completed
                successfully.
  
  The expectation is that the VM is assigned to the default data
  mover and the tag for the default data mover be associated with
  the VM in the VMware vSphere client GUI.
  
  After a second tagging-compatible scheduled backup run including
  
  a second VM and a second data mover tagged for the schedule, the
  
  default data mover tag is associated with the first VM and no
  data mover tag is associated with the second VM.
  
  
  Using 'VirtualMachine1' as an example of the name of the first
  
  VM, and DATA_MOVER_1 as the tagDefaultDataMover, messages like
  the following are logged in the scheduler log:
  
  [date] [time] Total number of virtual machines processed: 2
  [date] [time] ANS4313I Rebalance Schedule SCHEDULE_NAME Type:
                Minimal
  [date] [time] The data mover tag for 'VirtualMachine1' has been
                assigned to DATA_MOVER_1 for schedule
                SCHEDULE_NAME.
  [date] [time] Scheduled event 'SCHEDULE_NAME' completed
                successfully.
  
  
  The expectation is that the first VM should have already been
  assigned to the default data mover during the first scheduled
  backup and that the second VM should have been assigned to the
  second data mover during the second scheduled backup. This
  should also be reflected by the tag associations in the VMware
  vSphere client GUI after the second scheduled backup.
  
  
  =======================
  Affected product versions:
  IBM Spectrum Protect for Virtual Environments:
  Data Protection for VMware version 8.1.10 or later versions on
  all supported Windows and Linux platforms
  
  
  =======================
  Additional Keywords:
  
  TS006390077 tsm tsmve tag enabled
  
  | MDVREGR 8.1.10.0-TIV_5725TVEVM | IT31645
  

Local fix

• Manually rebalance the workload using the
  VMREBALANCESCHEDULEONLY option:
  https://www.ibm.com/docs/en/spectrum-protect/8.1.13?topic=tagsc
  hedule-using-option-rebalance-scheduled-operations
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect for Virtual Environments Data           *
  * Protection for VMware versions 8.1.10, 8.1.11, 8.1.12 and    *
  * 8.1.13 running on Microsoft Windows x64 and Linux x86_64     *
  * platforms.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in the Data Protection for VMware version 8.1.14 *
  * on Windows x64 and Linux x86_64 platforms. Note that this is *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• After the fix, the automatic rebalancing of a tagged schedule
  operation will work as expected.
  

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

• Fixed component name

  TSM FOR VE DP V

• Fixed component ID

  5725TVEVM

Applicable component levels