IBM Support

IT19972: BACKUP VM ANS0361I DIAG: VMSENDVIAFILE(): ERROR GETTING STATS FOR FILE XXXXXX.VMRS. HYPER-V 2016 ANS0361I ANS1228E ANS4005E

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a Hyper-V guest running in Windows Server 2016 Hyper-V host
    has a virtual machine configuration version lower than version
    8, the guest cannot be successfully backed up. The following
    error messages are seen in the dsmerror.log or dsmsched.log:
    
    03/28/2017 14:30:40 ANS0361I DIAG: vmSendViaFile(): Error
    getting stats for file C:\ClusterStorage\Volumename\VM\Virtual
    Machines\72E50214-2D30-40D8-A691-CE52C04C4772.vmrs.
    03/28/2017 14:30:50 ANS1228E Sending of object 'VM' failed.
    03/28/2017 14:30:50 ANS4005E Error processing 'VM': file not
    found
    
    Virtual machine configuration version 8 has been introduced with
    Windows 2016. Running a lower virtual machine configuration
    version on a Windows 2016 Hyper-V host typically happens during
    a rolling upgrade of a Hyper-V cluster.
    The virtual machine configuration version of the Hyper-V guest
    can be checked in the Hyper-V manager or using PowerShell
    Cmdlet:
      Get-VM * | Format-Table Name, Version
    
    When IBM Spectrum Protect for Virtual Environments - Data
    Protection for Microsoft Hyper-V is running on a Windows 2016
    Hyper-V host, the client assumes that the virtual machine has
    virtual machine configuration version 8. The client tries to
    backup a VMRS file that has been introduced in this
    configuration version, but this VMRS file is missing because the
    Hyper-V guest is using an older virtual machine configuration
    version, which doesn't have VMRS and VMCX files.
    
    IBM Spectrum Protect Versions Affected:
    IBM Spectrum Protect for Virtual Environments - Data Protection
    for Microsoft Hyper-V 8.1
    
    Initial Impact: High
    
    Additional Keywords: TSM, Tivoli, Storage, Manager, TDP, TDP4VE,
    

Local fix

  • There are two possible fixes:
    1 Backup the Hyper-V guest on a Hyper-V host matching the
      Hyper-V guest version if an older Hyper-V host is still
      available.
    2 Upgrade the Hyper-V guest version to version 8 if no such
      Hyper-V host is available. Follow these steps to upgrade to
      version 8:
       * Shutdown the Hyper-V guest
       * Run the PowerShell Cmdlet 'Update-VMVersion <vmname>'
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect for Virtual Environments Data           *
    * Protection for Hyper-V version 7.1 and 8.1 running on all    *
    * Microsoft Windows x64 platforms.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * This issue is projected to be fixed in the Backup-Archive    *
    * Client version 8.1.2 and 7.1.8 on all Microsoft Windows x64  *
    * platforms                                                    *
    * Note 1: The Backup-Archive Client is a part of the Data      *
    * Protection for Microsoft Hyper-V. In Data Protection for     *
    * Microsoft Hyper-V environments, the Backup-Archive Client is *
    * also known as the data mover.                                *
    * Note 2: This is subject to change at the discretion of IBM.  *
    ****************************************************************
    

Problem conclusion

  • Windows Server 2012 Hyper-V: VM configuration files has the xml
    file format. VM version is 5.0.
    Windows Server 2016 Hyper-V: format of VM configuration files
    has been changed from the xml file to a binary file format. VM
    version became 7.
    The problem was that in mixed-OS Failover Windows Cluster
    (Windows 2012 + Windows 2016) with Hyper-V role the VM version
    is 5 but data mover treated it as v7 and it leaded to the error.
    The code has been modified to correctly process virtual machine
    v5.0 in mixed-OS environment.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19972

  • Reported component name

    TSM VE DP MS HY

  • Reported component ID

    5725TVEHV

  • Reported release

    81W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-06

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

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

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

Modules/Macros

  • DSMC     DSM      DSMCSVC
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R81W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 81W

Reference #: IT19972

Modified date: 18 May 2017