Fixes are available
APAR status
Closed as program error.
Error description
The final BACKUP VM might be inconsistent. The root cause are incorrect counting of specific VM cases : 1. template VM guests counted as failed when the client option 'Vmenabletemplatebackups'=no (this is the default) 2. Orphaned VM guests (An orphan virtual machine is one that exists in the vCenter Server database but is no longer present on the ESX host. A virtual machine also shows as orphaned if it exists on a different ESX host than the ESX host expected by vCenter Server.) 3. VM guests specified in the client option 'domain.full' but that do not exist in the VMware environment the following stats will be incorrect : Total number of objects inspected Total number of objects backed up Total number of objects failed the following stats will be correct : Total number of virtual machines backed up successfully Total number of virtual machines failed Total number of virtual machines processed Here is an example of what can be seen : Total number of objects inspected: 10 <-- this should be 14 Total number of objects backed up: 3 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 11 Total number of subfile objects: 0 Total number of bytes inspected: 75.01 GB Total number of bytes transferred: 48.33 GB Data transfer time: 1,655.60 sec Network data transfer rate: 30,588.18 KB/sec Aggregate data transfer rate: 35,247.48 KB/sec Objects compressed by: 0% Total data reduction ratio: 35.62% Subfile objects reduced by: 0% Elapsed processing time: 00:23:56 Backup VM command complete Total number of virtual machines backed up successfully: 3 virtual machine x32 backed up to nodename SNACKBAR virtual machine rh6-64 backed up to nodename SNACKBAR virtual machine linux-64proxy backed up to nodename SNACKBAR Total number of virtual machines failed: 11 virtual machine winxp-32(template) <-- * virtual machine win7-64(template) <-- * virtual machine x64 <-- ** virtual machine winxp-64(template) <-- * virtual machine win7-32(template) <-- * virtual machine winxp-64 <-- *** virtual machine winxp-32 <-- *** virtual machine win7-32 <-- *** virtual machine win7-64 <-- *** virtual machine win7-32proxy <-- *** virtual machine win7-64proxy <-- *** Total number of virtual machines processed: 14 * Template backup are not supported. ** Orphaned *** In the domain.full list but VM does not exist in the inventory Tivoli Storage Manager Versions Affected: Tivoli Storage Manager client 6.4 and later on Windows and Linux Initial Impact: Medium Additional Keywords: tsm zz64 backup vm vmware statistice objects count
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: The following backup-archive client * * versions are affected on all supported * * Windows and Linux (data mover) platforms: * * * * - 6.4.0, 6.4.1 * * - 7.1.0 * **************************************************************** * PROBLEM DESCRIPTION: Error Description: * * The final BACKUP VM statistics might be * * * * inconsistent. * * * * The root cause are incorrect counting * * of specific VM cases : * * * * 1. template VM guests counted as * * failed when the client option * * 'Vmenabletemplatebackups'=no (this * * is the default) * * 2. Orphaned VM guests * * 3. VM guests specified in the client * * option 'domain.full' * * but that do not exist in the VMware * * * * environment * * * * The following stats will be incorrect: * * * * Total number of objects inspected * * Total number of objects backed up * * Total number of objects failed * * * * The following stats will be correct: * * * * Total number of virtual machines * * backed up successfully * * Total number of virtual machines * * failed * * Total number of virtual machines * * processed * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 6.4.2, 7.1.1. Note that * * until the fixing levels are available, this * * information is subject to change at the * * discretion of IBM. * **************************************************************** This problem was introduced in 6.4.0 when support for backing up vm templates was added. When this support was added the aggregate statistics were not updated to count the inspection of template backups.
Problem conclusion
The backup-archive client, when performing the role of data mover: 1. For template VM: If the VMENABLETEMPLATEBACKUPS is not set in the options file, in a command option or in a client options set, TSM will continue to count the VM as failed. Additionally, the data mover has been fixed to count it as inspected. If the option is set to NO in the options file, in a command option or in a client options set, TSM will not report on any template VMs that are part of the operation. In this case the template VMs will be skipped and will not be reflected in the aggregate statistics or the VM specific statistics. If the option is set to YES in the options file, in a command option or in a client options set, TSM will count template VMs in the inspected and success/failed counts in the aggregate statistics and VM specific statistics (this is the existing behavior). 2. Orphaned VMs: will be counted as inspected and failed in the aggregate statistics and VM specific statistics. 3. VMs which do not exist but are listed in DOMAIN.VMFULL will be counted as inspected and failed in the agggregate statistics and VM specific statistics.
Temporary fix
Comments
APAR Information
APAR number
IC98136
Reported component name
TSM FOR VE DP V
Reported component ID
5725TVEVM
Reported release
64W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-05
Closed date
2014-03-04
Last modified date
2014-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DSM DSMAGENT DSMC
Fix information
Fixed component name
TSM CLIENT
Fixed component ID
5698ISMCL
Applicable component levels
R64L PSY
UP
R64W PSY
UP
R71L PSY
UP
R71W PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"64W","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
07 January 2022