IBM Support

IT11785: RESTORE HYPER-V ANS2866E AN ERROR OCCURRED CREATING VIRTUAL MACHINE 'NAME'. ANS4311E RC=7131

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using Data Protection for Microsoft Hyper-V to restore a VM
    to an SMB 3.0 remote file share, the restore operation ends
    unsuccessfully with messages similar to these:
    
      Restoring VM configuration information for '<VM_name>'
       ** Unsuccessful **
      ANS2866E An error occurred creating virtual machine
        '<VM_name>'.
    
      >>>>>> Restore Processing Interrupted!! <<<<<<
    
      ANS4311E Full VM restore of 'Hyper-V' Virtual Machine
        '<VM_name>' failed with RC=7131 target
        node name='<NODE_NAME>', data mover node name='<NODE_NAME>'
    
    The dsmerror.log file has corresponding messages similar to
    these:
    
      10/09/2015 15:13:48 ANS0361I DIAG:
        vmBuildHypervRestorePaths(): Error creating path
        '\\<remote\share>\<directory>\<VM_name>\' .
    
      10/09/2015 15:13:48 ANS0361I DIAG:
        vmHyperVCreateNewVmMachine(): Error creating hyper-v restore
        path.
    
      10/09/2015 15:13:48 ANS2866E An error occurred creating
      virtual machine  '<VM_name>'.
    
      10/09/2015 15:13:49 ANS4311E Full VM restore of 'Hyper-V'
        Virtual Machine '<VM_name>' failed with RC=7131 target node
        name='<NODE_NAME>', data mover node name='<NODE_NAME>'
    
      10/09/2015 15:13:51 ANS2866E An error occurred creating
        virtual machine  '<VM_name>'.
    

Local fix

  • Map the remote share to a drive letter, then try the restore
    again, specifying the -vmname and -targetpath options. For
    example, if the SMB 3.0 remote file share is
    \\hypervsofs\SOFSShare1, the VM guest you want to restore is
    storman-win81, and the guest should be restored to directory
    \\hypervsofs\SFSShare1\Virtual Machine:
    
      net use x: \\hypervsofs\SOFSShare1
    
      dsmc restore vm storman-win81 -vmname=storman-win81
        -targetpath="X:\Virtual Machines"
    
    The dsmc restore command is one single command, even thought it
    is displayed here on two lines.
    
    Important:
    The first backup of the restored VM following the restore should
    include the -vmbackupupdateguid option:
    
      dsmc backup vm storman-win81 -vmbackupupdateguid
    
    Otherwise the backup of the newly restored VM will be
    unsuccessful:
    
      10/13/2015 13:50:05 ANS1715E A filespace already exists for
        virtual machine (storman-win81), but with a different
        virtual machine UUID (CBF80A99-5D51-479E-8E7D-F9BCE794924F)
        than the current virtual machine UUID
        (6D73646F-1EC6-496B-A88D-04B8712EF122).
    
      10/13/2015 13:50:07 ANS1228E Sending of object
        'storman-win81' failed.
    
      10/13/2015 13:50:07 ANS5226E The virtual machine backup
        operation failed.
    
    Note: This option is required only for the first backup after
    the restore. Thereafter, regularly scheduled backups should work
    correctly.
    

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                                        *
    *                                                              *
    * ERROR DESCRIPTION:                                           *
    * When user tries to restore a VM to a destination path        *
    * specified in UNC format restore process fails.               *
    * For example, following command will fail                     *
    *                                                              *
    * dsmc restore vm MYVM -vmname=MyVM-Restored                   *
    * -targetpath=\\machine\share\path                             *
    *                                                              *
    *                                                              *
    * LOCAL FIX:                                                   *
    *                                                              *
    * Map the network location to a local drive and re-try         *
    * restore. For example,                                        *
    * same scenario as above: try to restore MyVM to a new         *
    * location                                                     *
    *                                                              *
    * net use X: \\machine\share                                   *
    *                                                              *
    * dsmc restore MyVM -vmname=MyVM-Restored -targetpath=x:\path  *
    ****************************************************************
    * 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

  • Internal routine that creates destination path has been updated
    to correctly handle UNC path.
    

Temporary fix

  • A fix for this problem is currently targeted for Tivoli Storage
    Manager Client on Windows for interim fix package 7.1.4.1
    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

    IT11785

  • 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

    2015-10-14

  • 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

  • R71W PSN

       UP

[{"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:
26 September 2021