The following messages may appear in the powerShellDebug.log:
Host is
already in Paused state
Host state is suspended, there is no need to suspend the Host.
Error suspending
the Host : [exception message]
An exception occurred while trying to suspend the Host. Check the detail
provided in the exception message for more information.
The following message may appear in the EventLog:
Unable to
find a suitable Host to migrate VMs to.
A suitable host was not found to migrate VMs to.
The following messages may appear in the powerShellDebug.log:
Error getting
Clustered VMs List: [error message]
An error occurred retrieving a list of Highly Available VMs in the Custer,
check the error message for more information.
There are
no VMs to migrate
All Highly Available VMs are already powered off or there are not Highly
Available VMs on the host.
There are no target nodes for migration
No target nodes were found to migrate VMs to. Verify that hosts have been
added using the Select Target Hosts for Migration
option.
Error no
time left for migration
VM Migration did not complete within the given time period. The VM Migration
duration may need to be increased to allow enough time for this to complete.
Unable to
find target node [Host] for migration
Unable to find the target node in the cluster to migrate VMs to. This may
occur if a Host that was added using Select Target
Hosts for Migration option no longer exists in the Failover Cluster
or was re-named.
Error no time left to migrate VM [VM]
VM Migration did not complete within the given time period and as a result
there was not enough time to migrate the VM. The VM Migration duration
may need to be increased to give enough time for this to complete.
Error migrating
VM [VM] to target node [target] : [error message]
An error occurred while migrating a VM to the target node, check the error
message for more information.
Error migrating
VM [VM] to target node [target] : [exception message]
An exception occurred while migrating a VM to the target node, check the
exception message for more information.
Target node
[target] not available for migration
The state of the target node is not currently “Up” so VMs cannot be migrated
to it.
Error using
target node [target] for migration: [exception message]
An exception occurred while migrating VMs to the target node, check the
exception message for more information.
Unable to
migrate VMs : [VMs]
There was a problem while migrating all VMs to target nodes.
Error migrating
VMs: [exception message]
An exception occurred while migrating VMs, check the exception message
for more information.
The following messages may appear in the powerShellDebug.log:
There are
no VMs to shutdown.
No powered on VMs were found on the Host to shutdown.
Error shutting
down cluster VM [VM] : [error_message]
An error occurred while shutting down the VM, check the error message for
more information.
Shutdown
failed, power down non-clustered: [VM]
Unable to shutdown the non-clustered VM. PowerChute will attempt to power
down the non-clustered VM. This will occur when Integration Services are
not installed on the VM or the Guest OS Shutdown option in Integration
Services has not been enabled.
Error powering down VM [VM] : [error_message]
An error occurred while powering down the VM, check the error message for
more information.
Error shutting down VMs: [exception message]
An exception occurred while shutting down VMs, check the exception message
for more information.
The following messages may appear in the powerShellDebug.log:
Host is
already in Up state
The state of the Host is Up, there is no need to resume the Host.
Error resuming
the Host : [exception message]
An exception occurred while trying to resume the Host. Check the
detail provided in the exception message for more information.
The following messages may appear in the EventLog:
Attempting
to power on VMs that did not start.
If there was a problem powering on VMs PowerChute will re-attempt
to power on VMs that did not start.
The following messages may appear in the powerShellDebug.log:
There are
no VMs to start
There are no cluster or non-cluster VMs to start.
Error starting
the cluster VM [VM] : [error message]
An error occurred while starting the cluster VM, check the error message
for more information. The VM will get added to the reattempt VM startup
list (if not already on the list)
Error VM
startup failed for cluster VM [VM]
An error occurred while starting the cluster VM.
The VM will get added to the reattempt VM startup list (if not already
on the list).
Error starting
the non-cluster VM [VM] : [error message]
An error occurred while starting the non-cluster VM, check the error message
for more information. The VM will get added to the reattempt VM startup
list (if not already on the list)
Error VM
startup failed for non-cluster VM [VM]
An error occurred while starting the non-cluster VM.
The VM will get added to the reattempt VM startup list (if not already
on the list).
Removing
VM as it does not exist on this Host
The non-cluster VM has been removed from the VM startup list as it does
not exist on the Host.
Error starting
VM [VM] : [exception message]
An exception occurred while starting VMs, check the detail provided in
the exception message for more information.
Check if
Cluster service is running
An exception occurred while starting VMs, check if Cluster service is running.
When a Hyper-V Host is being shut down Failover Clustering will move its VMs to another available node in the Cluster if possible. This occurs even if those VMs have been powered off. When critical UPS events occur at different times this can lead to all VMs being located on the last available node in the cluster. This can cause issues when VM Startup is enabled in PowerChute if that Host has insufficient resources to start the VMs. Failover Cluster does not automatically fail back VMs to their original host.
In order for PowerChute to power on VMs that are running on a different node in the cluster to the one on which PowerChute is installed, it is necessary to modify the security permissions for the Cluster Computer Object in Active Directory, as outlined below:
Open Active Directory Users and Computers.
In the View menu select Advanced Features.
Click on the Computers container in the left hand pane.
Select the Cluster computer account in the right hand pane.
Double click on the Cluster computer account to open the properties dialog and go to the Security tab.
Click Add.
Click Object Types and enable Computers. Click OK.
Enter the Failover Cluster node machine name on which PowerChute is installed.
Grant Full Control.
Click Apply.
Repeat steps 8-10 for each node in the Failover Cluster on which PowerChute is installed.