IBM Support

Known Issues and Limitations: Data Protection for Microsoft Hyper-V V8.1

Preventive Service Planning


Abstract

This document details the Known Issues & Limitations for IBM® Spectrum Protect™ for Virtual Environments: Data Protection for Microsoft Hyper-V V8.1.

Content

This document is divided into linked sections for ease of navigation. Use the following links to jump to the section of the document that you require.


Data Protection for Microsoft Hyper-V Management Console Issues and Limitations

  • A VM backed up on Windows Server 2012 or 2012 R2 Hyper-V host by using Data Protection for Hyper-V 7.1.8 should be restored by using Windows Server 2012 or 2012 R2. (internal reference #188855)
    Problem: A VM that was backed up by using IBM Spectrum Protect Data Protection for Hyper-V version 7.1.8 might fail to restore by using a newer version of Data Protection for Hyper-V on Windows Server 2016 or higher.
    Problem Verification: If during restoring a VM by using Data Protection for Hyper-V version 8.1.0 or higher the message:

    ANS2866E An error occurred creating virtual machine

    is displayed and the VM was originally backed up on Windows 2012 or 2012 R2 by using Data Protection for Hyper-V 7.1.8 then this issue was encountered.
    Workaround: To migrate a VM from Windows Server 2012 or 2012 R2 to Windows Server 2016 or higher the VM can be exported by using Hyper-V Manager or PowerShell and then imported on Windows Server 2016 or higher again by using Hyper-V Manager or PowerShell.  If needed the VM can first be restored to the Windows Server 2012 or 2012 R2 host by using Data Protection for Hyper-V 7.1.8.
    Affected platforms: Windows
    Limitation: Since V8.1.9.
     

  • Some files that are deployed with Data Protection for Hyper-V do not have correct metadata. (internal reference #187269)

    Problem: Data Protection for Hyper-V includes the following components:
    • IBM Spectrum Protect JVM
    • IBM Spectrum Protect for Virtual Environments: Recovery Agent
    • IBM Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V
    • IBM Spectrum Protect for Virtual Environments: Framework
    • IBM Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V suite
    • IBM Spectrum Protect Client
    • IBM Spectrum Protect WebServer
    Files that belong to each component include metadata such as file version, description, copyright and company information. For some of the files in these components the metadata is not up to date. There are no symptoms or side effects related to this issue other than if the affected files were viewed in Windows Explorer, for example, the metadata might look as expected.
    Workaround: Ignore the missing or incorrect metadata.  It is updated in an upcoming release.
    Affected platforms: Windows
    Limitation: Since V8.1.9.


     

  • When Data Protection for Hyper-V is deployed on Windows Server 2012 and after the configuration wizard completes the message ANS5060E Invalid parameter passed might be displayed in the UI instead of a list of VMs (internal reference #183043)

    Problem: This issue might occur when the following conditions are met:
    • The Hyper-V host is running Windows Server 2012
    • The IBM Spectrum Protect server administrative account has sessionsecurity set to strict
    • File restore support was selected during configuration
    • "ANS5060E Invalid parameter passed" appears in the Data Protection for Hyper-V MMC main window
    Workaround:
    • One workaround is to update the IBM Spectrum Protect administrative account used to have sessionsecurity=transitional and rerun the configuration wizard.
    • Another workaround, which avoids having to update the Admin account is to rerun the configuration wizard and do not choose File Restore support.  Repeat the configuration wizard a second time and select File Restore support.
    Affected platforms: Windows
    Limitation: Since V8.1.8.


     

  • IBM Spectrum Protect Client UI "Edit" -> "Java Diagnostic" dialog box shows an incorrect operating system - Windows Server 2016 (internal reference # 179755 & # 179754)
    Problem: On Windows 2019, the field display Windows 2016 instead of Windows 2019. It is a display issue and does not impact functionality.
    Workaround: None.
    Affected platforms: Windows
    Limitation: Since V8.1.7.
     

  • The Help menu item Help on Data Protection for Microsoft Hyper-V does not display help (internal reference #177407)
    Problem: Data Protection for Hyper-V uses web-based online help and does not provide Compiled HTML Help (CHM), which is used by Microsoft Management Console.
    Workaround: Access online help by using one of the following methods:

    • Click one of the help links in the Actions pane.
    • Click Data Protection for Hyper-V in the navigation pane and select one of the help links on the welcome page.

    Affected platforms: Windows
    Limitation: Since V8.1.7.
     

  • Might need to click Verify Node twice to see the status of a Linux mount proxy node in the Data Protection for Hyper-V MMC UI (internal reference #170642)
    Problem: The Data Protection for Hyper-V MMC UI includes a Properties menu item in the Action pane. Clicking it brings up a property sheet, which includes a Verify Nodes page. When a Windows mount proxy node is selected and the Verify Node button is clicked the status is normally returned for both the Windows and Linux mount proxy nodes.  If then the mount proxy CAD service is not running then the CAD will be started and the information will return for the Windows mount proxy but the Linux mount proxy node information will be blank.
    Workaround: Click the Verify Node button a second time and the Linux mount proxy information will be displayed.
    Affected platforms: Windows
    Limitation: Since V8.1.6.
     

  • Backing up VM disk on MMC GUI with "include disk 1 only" or "Include all except disk 1" will not work (internal reference #158261)
    Problem: Backing up vm disk on MMC GUI with "include disk 1 only" or "Include all except disk 1" will not work. It will still backup all disks.
    Workaround:

    1. Backup disk by using Backup-DpHvVm powershell cmdlet:

      Backup-DpHvVm -VmName <vm>  -diskProtection "Disk1Only"  ---- include disk1 only
Backup-DpHvVm -VmName <vm>  -diskProtection "AllExceptDisk1"  ---- include all except disk 1

    2. Backup disk by using dsmc backup vm command:

      1. dsmc backup vm vmname:vhdx=disk_location

      2. with the following option in opt file.

        INCLUDE.VMDISK--vmname-- -disk_location
INCLUDE.VMDISK--vmname-- -disk_location

    Affected platforms: Windows
    Limitation: Since V8.1.4. Solved with V8.1.6, see APAR IT23489.
     

  • When Application Protection is enabled for a VM and a backup operation is initiated the MMC UI will present a dialog, which contains Data Consistency choices, which don't apply (internal reference #165236)
    Problem: The MMC UI does not provide an option that reflects Application Protection.  When Application Protection is enabled for a VM by specifying include.vmtsmvss <vmname> in the data mover options file it will override the behavior of the options in the Data Consistency drop down list.
    Workaround: None.  Be aware that the include.vmtsmvss option in the data mover option file will override the options in the Data Consistency drop down list on the backup dialog in the MMC UI.
    Affected platforms: Windows
    Limitation: Since V8.1.6.
     

  • A menu is not properly displayed in the MMC UI (internal reference #161118)
    Problem: When right-clicking on an item in the MMC UI the menu is not properly displayed. It might appear as a thin rectangle instead of a menu.
    Workaround: Re-select the items and right-click again to see the menu or re-select the items and choose an action in the Actions pane.
    Affected platforms: Windows
    Limitation: Since V8.1.6.
     

  • An operation might time out while waiting to execute (internal reference #160855)
    Problem: A backup or restore operation is initiated and is placed in the MMC task list until other operations have completed.  If the operation waits longer than the session timeout (30 minutes) then the waiting tasks will not be executed.
    Workaround: Resubmit the operation
    Affected platforms: Windows
    Limitation: Since V8.1.6.
     




 


Data Mover Issues and Limitations

  • Data Protection for Microsoft Hyper-V supports back ups of VMs on SMB3 (internal reference #159308)
    Problem: However, there is an exception for Linux and FreeBSD VMs.
    For more information, see the following Microsoft TechNet article https://technet.microsoft.com/en-us/library/dn531031.aspx and excerpt under Feature Descriptions for Linux and FreeBSD virtual machines on Hyper-V -> Storage -> Live virtual machine backup:

    "Note that the backup operation does not succeed if the virtual machine has virtual hard disks (VHDs) that are hosted on remote storage such as a Server Message Block (SMB) share or an iSCSI volume. Additionally, ensure that the backup target does not reside on the same volume as the volume that you back up."
    Workaround: None.
    Affected platforms: Windows
    Limitation: Since V7.1 and V8.1 releases
     

  • Delete backup command is not supported (internal reference #159309) 
    Problem: In this scenario, a delete backup command is issued for an existing virtual machine backup. However, the following message displays:

    ANS2314E No VM backup exists for <vmname>

    This error displays for an existing virtual machine backup because the delete backup command is not supported. This is a known limitation.
    Workaround: None.
    Affected platforms: Windows
    Limitation: Since V7.1 and V8.1 releases
     

  • LANFREE backup of a virtual machine that does not succeed due to lack storage space returns an incorrect error code of -72 instead of 29 (internal reference #147639)
    Problem: When backing up a virtual machine by using LANFREE and the backup stops due to lack of storage space on the server the wrong error code will be displayed.  The correct error code for this situation is 29, but the backup operation will return -72 in logs and on the extended summary table.  Both messages corresponding to each error code, 1329S for 29 and 1235E for -72 will be displayed and logged.
    Problem Verification: If the backup operation was conducted over LANFREE and did not succeed with error code -72, the backup operation will also have logged the message 1329S, is logged when the server indicates an out of storage space situation.
    Workaround: No workaround, the backup will succeed when there is sufficient storage space in the assigned storage pool on the server.
    Affected platforms: Windows
    Limitation: Since V8.1.2.
     

  • Incremental backups for VMs with differencing disks on different volumes are failing (internal reference #147609)
    Problem: Hyper V guest VMs that are configured with differencing disks fail incremental backups. When a snapshot is taken it is placed where the child disk is located. When we search for the parent disk it will not be found since it is not in the same location as the child disk, thus failing the incremental backup.
    Workaround: VMs with differencing disks should have all disks on the same volume.
    Affected platforms: Windows
    Limitation: Since V8.1.2.
     

  • ANS2731E or ANS2751E is reported incorrectly as backing up or restoring Hyper-V virtual machine (internal reference #146587)
    Problem: If the Hyper-V role is not enabled and the dsm.opt is not configured with VMBACKUPType HYPERVFULL entry, backing up virtual machine command results in the following error message:

    ANS2731E The BACKUP VM command failed because the Data Protection for VMware license file does not exist or is not valid.

    And, restoring virtual machine command results in the following error message:

    ANS2751E The RESTORE VM command failed because the Data Protection for VMware license file does not exist or is not valid.

    Workaround: Configure the dsm.opt file and make sure the VMBACKUPType HYPERVFULL is added. Then, the correct information about Microsoft Hyper-V is reported.
    Affected platforms: Windows
    Limitation: Since V8.1.2.



 


Mount Proxy Issues and Limitations

  • Instant Access operation will fail on win2016 cluster environment (internal reference #177751)
    Problem: When Instant Access operation on win2016 cluster environment, you might see the process fails to create a new IA vm.
    The root cause is due to the cmdlet get-iscsisession | get-disk fails to return the disk number for next action.
    Workaround:  None.
    Affected platforms: Windows
    Limitation: Since V8.1.7.

  • Instant Access does not support dynamic disks (internal reference #173173)
    Problem: If an Instant Access operation is used with a VM that has dynamic disks the operation will fail with message ANS2411E.
    Workaround: None.
    Affected platforms: Windows
    Limitation: Since V8.1.6.
     

  • Instant Access is not supported for SUSE Linux 11.x (internal reference #173650)
    Problem: After an Instant Access restore of a VM based on SUSE 11.x the VM will not start.
    Problem Verification: If Instant Access is used with a VM based on SUSE Linux 11.x note that the VM cannot be started after the Instant Access operation completes.
    Workaround: Update the VM to a version of SUSE Linux that is supported for Instant Access.
    Affected platforms: Windows
    Limitation: Since V8.1.6.



 


Recovery Agent Issues and Limitations

  • Microsoft BitLocker encryption not supported (internal reference #200411 and #202189)
    Problem: File-level restore for BitLocker-encrypted drives on Windows virtual machines is not possible.
    This limitation applies to file-level restore in all versions of VMware and Microsoft Hyper-V environments.
    Workaround: n/a
    Affected platforms: Windows
    Limitation: Since V8.1. Solved with 8.1.12, see APAR IT36049.
     

  • During a Data Protection for Microsoft Exchange Server or Microsoft SQL Server database restore operation by using the VMVSS method in the Hyper-V guest, Microsoft Windows Defender might prevent the database volume from being brought online from the IBM Spectrum Protect server (internal reference # 170435)
    Problem: This issue affects Data Protection for Microsoft Hyper-V V8.1.6 and later. During virtual disk iSCSI volume mounts from the IBM Spectrum Protect server, the Microsoft Windows Defender program might prevent the volume from being online. This issue will cause Data Protection for Microsoft Exchange Server or Microsoft SQL Server to not be able to restore databases with the VMVSS method. The Windows disk manager is unable to mount the iSCSI volume from the IBM Spectrum Protect server during SQL or Exchange restore operations.
    When Microsoft Windows Defender is enabled in the Hyper-V guest system that is hosting Microsoft SQL Server or Microsoft Exchange Server.
    Error message:

    ANS5266E File-level copy restore of 'DB01' failed.

    Trace:

    exceeding VSS_RESTORE_RECONNECT_TIME

    Problem Verification: The iSCSI mounted volume cannot be brought online or dismounted before the Data Protection for Microsoft Exchange Server or SQL Server restore operation is completed.    
    Workaround: Update the Windows Defender virus and threat protection settings to exclude the IBM Spectrum Protect recovery agent. Complete the following steps:

    1. Open the Windows Defender settings window.
    2. Locate the Exclusions section and click Add an exclusion.
    3. Click the plus sign (+) next to Exclude a .exe, .com, or .scr process.
    4. In the Add exclusion window, enter "RecoveryAgent.exe" and click OK.
    5. Close the Windows Defender Settings window.
       
    Affected platforms: Windows
    Limitation: Since V8.1.6.



 


Installation Issues and Limitations

  • The metadata for some of the files deployed with Data Protection for Microsoft Hyper-V is not up to date (internal reference #185331)
    Problem: This issue is informational only and does not affect the operation of Data Protection for Microsoft Hyper-V in any way.  Some of the deployed files are:

    • Not digitally signed by IBM
    • Missing 'IBM Corporation' from the company information property
    • Missing a 2019 Copyright statement
    • Not versioned

    Workaround: Ignore the missing information.  
    Affected platforms: Windows
    Limitation: Since V8.1.8.
     

  • Data Protection for Microsoft Hyper-V suite installer does not check that enough space is available on disk (internal reference #158549)
    Problem: During the installation of IBM Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V suite a user might see this message displayed:

    The wizard was interrupted before the IBM Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V suite could be completely installed.

    One cause for the failure is the user does not have enough disk space to install the product. The application will fail to install the under lying packages. The user will need to look in the C:\ProgramData directory at the last package that was being installed to see whether there is an out of space error. The message will be something like this:

    MSI (s) (54:B8) [22:22:18:203]: Note: 1: 1601 2: C: 3: 426,174 4: 223,580
Disk full: Out of disk space -- Volume: 'C:'; required space: 426,174 KB; available space: 223,580 KB.  Free some disk space and retry.
MSI (s) (54:B8) [22:22:18:250]: Product: IBM Spectrum Protect Client -- Disk full: Out of disk space -- Volume: 'C:'; required space: 426,174 KB; available space: 223,580 KB.  Free some disk space and retry.

    Workaround: The user will need to uninstall the packages manually in Programs and Features that the Suite Installer laid down, free up space on the computer, rerun the Suite Installer.
    Affected platforms: Windows
    Limitation: Since V8.1.4. Solved with V8.1.6, see APAR IT23487.



 


Other Issues and Limitations

  • Dsmerror.log might include garbled text for message ANS1577I after an uninstall. (internal reference #203296)
    Problem: After an uninstall, dsmerror.log might include unreadable text for message ANS1577I.
    Workaround: The message can safely be ignored.
    Affected platforms: Windows
    Limitation: Since V8.1.12.
     

  • Instant access or virtual machine restore: Unable to power up when ISO file was mounted from user desktop (internal reference #176979)
    Problem: A Hyper-V virtual machine might fail to start after running a restore operation. This might occur if an ISO image was mounted to the virtual machine when the backup was taken and if the Hyper-V virtual machine Management service account does not have permission to the location where the ISO image was mounted from. In this case, an error message similar to the following might appear when starting the virtual machine:

    An error occurred while attempting to start the selected virtual machine(s).
Synthetic SCSI Controller Failed to Power on with Error 'General access denied error.'b
Hyper-V Virtual Machine Management service account does not have permissions to open attachment <path to ISO image>.

    Workaround: With the virtual machine powered off open the virtual machine's settings and select the DVD drive that refers to the ISO image referenced in the error message. Under the Media section, where it says to specify the media to use, select None. Now the virtual machine can be powered on and optionally the ISO image can be remounted.
    Affected platforms: Windows
    Limitation: Since V8.1.7.



 

[{"Product":{"code":"SSERB6","label":"IBM Spectrum Protect for Virtual Environments"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for Microsoft Hyper-V","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
23 September 2021

UID

swg21993768

Page Feedback