Product Documentation
Abstract
This document contains updates for IBM Storage Protect™ for Virtual Environments: Data Protection for Microsoft Hyper-V documentation.
Content
Documentation updates for Data Protection for Microsoft Hyper-V 8.2
No documentation updates are currently available for Data Protection for Microsoft Hyper-V 8.2.
Documentation updates for Data Protection for Microsoft Hyper-V 8.1
- Documentation missing best practice information for Data Protection for Microsoft Hyper-V
The IBM Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V 8.1.0 documentation includes topics entitled: Hyper-V backup support limitations and Determine system requirements, which both exclude best practice information.
The Hyper-V backup support limitations topic excludes the paragraph "To backup virtual machines that exist on shared CSV storage across multiple Data Protection for Microsoft Hyper-V hosts, it is best practice to run backups on one host at a time. In such a configuration, this best practice helps to avoid "snapshot in progress" errors.” This missing information will be added to this topic.
The Determine system requirements topic excludes the sentence "To ensure robustness and performance, it is also best practice to use a VSS hardware provider rather than a software provider.” This missing information will be added to this topic.
Documentation missing limitation for backup of VM disks greater than 2 TB (V8.1.4 and earlier versions)
The Hyper-V backup support limitations topic in V8.1.4 and earlier versions excludes the paragraph "You cannot back up VM disks that are greater than 2 TB. Do not include VM disks that are greater than 2 TB in VM backup operations."
Parameter update required for Data Protection for Microsoft Hyper-V cmdlet example
The Data Protection for Hyper V cmdlet examples topic describes how to protect your Hyper-V Virtual machines by using cmdlets.
The following parameter information is updated in the "Data Protection for Hyper-V cmdlet examples" topic:
Example 4: Store IBM Spectrum Protect server connection information on the Hyper V host and verify the connection
$cred = Get-Credential -Message "Enter credentials" -UserName user_name $session = New-DpHvSession -ComputerName computer_name -Credential $cred Set-ServerConnection -Session $session -ServerName server_name -Admin ` admin_name -AdminPwd admin_password -ServerSSLPort port Remove-DpHvSession -Session $session
If you backed up data to the IBM Spectrum® Protect server, Data Protection for Microsoft Hyper-V can automatically fail over to the failover server for data recovery when there is an outage on the IBM Spectrum Protect server.
The server that the IBM Spectrum Protect data mover node connects to during normal production processes is called the primary server. When the primary server and data mover node are set up for node replication, the client data on the primary server can be replicated to another IBM Spectrum Protect server, which is the failover server.
During normal operations, connection information for the failover server is automatically sent to the data mover node from the primary server during the logon process. The failover server information is automatically saved to the client options file on the data mover node. No manual intervention is required by you to add the information for the failover server.
Each time the data mover node logs on to the server, it attempts to contact the primary server. If the primary server is unavailable, the data mover node automatically fails over to the failover server, according to the failover server information in the client options file. In failover mode, you can restore any replicated client data. When the primary server is online again, the data mover node automatically fails back to the primary server the next time the data mover node connects to the server.
Requirements: Before the connection information for the failover server is sent to the client options file, the following processes must occur:
- The primary server, failover server, and data mover node must be at the version 7.1 level.
- The primary and failover servers must be set up for node replication, and the client node must be configured for node replication on the server.
- You must back up Hyper-V data at least one time to the primary server.
- Client data on the primary server must be replicated to the failover server at least one time.
Restriction: The following restrictions apply to Data Protection for Microsoft Hyper-V during failover:
- Any operations that require data to be stored on the server, such as backup operations, are not available.
- Schedules are not replicated to the failover server. Therefore, schedules are not run while the primary server is unavailable.
- Validation of virtual machine backups is not available.
- All client failover scenarios using the Data Protection for Microsoft Hyper-V MMC GUI and the IBM Spectrum Protect file restore interface are not operational. As a workaround, you can use the dsmc command line on the data mover node to only restore data from the failover server (with the exception of VM file level restore, which is not available with the dsmc command). You can run a full VM restore, or instant access operation by using the restore vm command with the vmrestoretype option. For more information, see Vmrestoretype.
Related Information
Was this topic helpful?
Document Information
Modified date:
11 December 2025
UID
swg27048970