
•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:
•Scenario 6: Retention is invalid.
Retention specified is invalid. Valid:
•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
Preconditions
The user must first login with
Syntax
Any optional parameters require square brackets [ ] around them.
Table 39 Get-ClusterNodeNames parameters
Parameter | Optional/Required | Description |
Required | Host name of the RMH Server. This is | |
|
| FQDN or IP address. |
| Required | Optionally select |
|
| to use. If not specified, |
|
| host/cluster must be selected using |
|
| |
|
| address. Synonyms for |
|
| supported. The localhost is not |
|
| supported. |
Optional | Displays progress messages. |