A fix is available
APAR status
Closed as program error.
Error description
If a Microsoft Hyper-V Virtual Machine (VM) has a virtual disk residing on a SMB 3.0 remote share, and the share name is in the form of a fully qualified domain name (FQDN), then a Data Protection for Microsoft Hyper-V backup of that VM does not complete successfully. External symptoms include these messages: ANS8060E Error validating file '\\HYPERVCLUS1\SOFSSHARE1@{BE05C39E-B30B-45E9-8743-7AA3B16549D9} \rg\sofsshare1\Win2012 - FQDN\Win2012 - FQDN\Virtual Hard ANS4308E Full VM backup of 'Hyper-V' Virtual Machine 'Win2012 - FQDN' failed with RC=4379 mode=Incremental Forever - Full, target node name='HYPERVCLUS', data mover node name='HYPERVCLUS-AGENT4' ANS1228E Sending of object 'Win2012 - FQDN' failed. ANS5226E The virtual machine backup operation failed. Note: The ANS8060E message might not always be logged. This problem exists in the Data Protection for Microsoft Hyper-V data mover (backup-archive client) versions 7.1.1 - 7.1.4. Diagnosing this problem: * Message ANS8060E is a good indicator that the VM cannot be backed up due to this APAR. However, as noted above, this message might not always be issued. * Examine the VM's disks to see if any disk resides on a fully- qualified domain name remote share. An example of a fully- qualified share name is: \\hypervsofs.amrhyperv.org\sofsshare1\Win2012 - FQDN\Win2012 - FQDN\Virtual Hard Disks\Win2012 - FQDN.vhdx as opposed to a name that is not fully qualified: \\hypervsofs\sofsshare1\Win2012 - FQDN\Win2012 - FQDN\Virtual Hard Disks\Win2012 - FQDN.vhdx * If the backup operation is traced with trace flag HYPERV, look for messages like these in the trace. Note that the date and time stamps, process and thread IDs, and parent directories of the source file names are not shown. vsssnap.cpp( 949): CreateSnaps() Getting file 3 out of 5 vsssnap.cpp( 957): CreateSnaps() backup this (path) : \\hypervsofs.amrhyperv.org\sofsshare1\Win2012 - FQDN\Win2012 - FQDN\Snapshots vsssnap.cpp( 959): CreateSnaps() backup this (fspec) : 58AA091E-104D-405B-A2D0-A1B9477B5E02.xml vsssnap.cpp( 960): CreateSnaps() backup this masque : 0x10505 vsssnap.cpp( 962): CreateSnaps() Is recursive : 0 File mask 10505 vsssnap.cpp( 967): CreateSnaps() Path and filespec only occur on snapshot vsssnap.cpp( 970): CreateSnaps() Skip filespec since does not exist on current drive vsssnap.cpp( 996): CreateSnaps() Found filespec on snapshot: \\hypervsofs.amrhyperv.org\sofsshare1\Win2012 - FQDN\Win2012 - FQDN\Snapshots\58AA091E-104D-405B-A2D0-A1B9477B5E02.xml
Local fix
One possible workaround is to change the fully qualified share name to a non-fully qualified name. IBM recognizes that this workaround might not be feasible in all environments. 1. Shut down the VM. 2. Modifiy the VM's disks to use non-fully qualified share names. 3. Restart the VM. 4. Try the backup operation again.
Problem summary
**************************************************************** * USERS AFFECTED: * * Tivoli Storage Manager for Virtual Environments component * * Data Protection for Microsoft Hyper-V versions 7.1.1, 7.1.2, * * 7.1.3 and 7.1.4 * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * This issue is projected to be fixed in the Tivoli Storage * * Manager Client on Windows 7.1.6 * * Note 1: The Tivoli Storage Manager (TSM) Client is a part of * * the Data Protection for Microsoft Hyper-V. In Data * * Protection for Microsoft Hyper-V environments, the TSM * * Client is also known as the data mover. * * Note 2: This is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
During HyperV VM backup VHDX file check fails because VHDX file name is in UNC format. Code has been updated to handle file names in UNC format.
Temporary fix
A fix for this problem is currently targeted for Tivoli Storage Manager Client on Windows for interim fix package 7.1.4.2 Note 1: The Tivoli Storage Manager (TSM) Client is a part of the Data Protection for Microsoft Hyper-V. In Data Protection for Microsoft Hyper-V environments, the TSM Client is also known as the data mover. Note 2: This is subject to change at the discretion of IBM.
Comments
APAR Information
APAR number
IT13165
Reported component name
TSM CLIENT
Reported component ID
5698ISMCL
Reported release
71W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-13
Closed date
2016-02-05
Last modified date
2016-03-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
dsmc.exe
Fix information
Fixed component name
TSM CLIENT
Fixed component ID
5698ISMCL
Applicable component levels
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"71W"}]
Document Information
Modified date:
13 February 2021