HP 3PAR Recovery Manager 1.1.0 Software for Microsoft Hyper-V User Guide (QL226-96343, June 2013)

Scenario 4: Cannot communicate with the VMs.
VM is specified, but RMH Server cannot communicate with specified VMs.
Scenario 5: Expiry is invalid.
Expiry specified is invalid. Valid: 1-43800h, 1-1825d.
Scenario 6: Retention is invalid.
Retention specified is invalid. Valid: 1-336h, 1-14d.
Scenario 7: VM(s) are not running.
VM(s) that are to be backed up must be running.
Scenario 8: License is missing for RMH.
License is missing for RMH.
Scenario 9: License is missing for Storage System Virtual Copy.
License is missing for Storage System Virtual Copy.
Scenario 10: VHD(s) are not on NTFS volumes.
VHDs need to reside on NTFS volumes.
Scenario 11: VSS is not operational.
VSS is not operational or not installed.
Scenario 12: VSS requestor fails.
VSS requestor fails during backup. Reason is displayed.
Scenario 13: Multiple Storage Systems is not supported.
RMH does not support multiple Storage Systems for VM.
Get-ClusterNodeNames
Get-ClusterNodeNames retrieves node names for the Hyper-V cluster.
Preconditions
The user must first login with Login-Rmh.
Syntax
Any optional parameters require square brackets [ ] around them.
Get-ClusterNodeNames -RmhServerName <RmhServerName> -HypervName
<HypervName> [-Verbose]
Table 39 Get-ClusterNodeNames parameters
DescriptionOptional/RequiredParameter
Host name of the RMH Server. This is
FQDN or IP address.
Required-RmhServerName
Optionally select Hyper-V host/cluster
to use. If not specified, Hyper-V
Required-HypervName
host/cluster must be selected using
Select-Hyperv. This is FQDN or IP
address. Synonyms for Hyper-V are
supported. The localhost is not
supported.
Displays progress messages.Optional-Verbose
Get-ClusterNodeNames 67