Applies to SnapManager for Hyper-V (SMHV) 2.1.2 and later Issue Dataset cannot be created because SMHV doesn't show high availability VMs in Create Dataset Wizard. SMHV doesn't show high availability ...Applies to SnapManager for Hyper-V (SMHV) 2.1.2 and later Issue Dataset cannot be created because SMHV doesn't show high availability VMs in Create Dataset Wizard. SMHV doesn't show high availability VMs under "Unprotected resources" in "Hosts" tab. SMHV shows VMs that are not clustered.
Switched cluster with existing non AFF A320 nodes AFF A320 nodes report takeover is disabled due to unsynchronized log in EMS: monitor.globalStatus.critical: Controller failover of <node> is not possi...Switched cluster with existing non AFF A320 nodes AFF A320 nodes report takeover is disabled due to unsynchronized log in EMS: monitor.globalStatus.critical: Controller failover of <node> is not possible: unsynchronized log. cf.fsm.takeoverOfPartnerDisabled: Failover monitor: takeover of <node> disabled (unsynchronized log). Waiting for <partner-node>, Takeover is not possible: Storage failover interconnect error, NVRAM log not synchronized, Disk inventory not exchanged
Applies to ONTAP 9 Issue Give-back fails with the following error message: ::> storage failover giveback -ofnode node-1 Error: command failed: Failed to initiate giveback. Reason: Unable to read partn...Applies to ONTAP 9 Issue Give-back fails with the following error message: ::> storage failover giveback -ofnode node-1 Error: command failed: Failed to initiate giveback. Reason: Unable to read partner state.
Verification fails at the attach database phase of the process Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have ...Verification fails at the attach database phase of the process Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it. Could not find database 'database_name__Clone'. The database either does not exist, or was dropped before a statement tried to use it. Verification done via SQL Management studio without SMSQL using the command below also fails with the same error
If a job fails to backup one or more VMs a snapinfo snapshot is not created. If a restore is required then this can still be done successfully, BUT the failed VM in the backup will not be restored. A ...If a job fails to backup one or more VMs a snapinfo snapshot is not created. If a restore is required then this can still be done successfully, BUT the failed VM in the backup will not be restored. A successful backup will show the snapinfo snapshot creation in the Job Report in \installation_path\NetApp\SnapManager For Hyper-V\SnapManager For Hyper-V Reports\Reports\Backup\: From the failed backup, the backup registers but the snapinfo snapshot creation is skipped:
