Search

SMHV: How to add new hosts to the existing Windows Failover Cluster
https://kb.netapp.com/Legacy/SnapManager/SMHV__How_to_add_new_hosts_to_the_existing_Windows_Failover_Cluster
Applies to FlexPod SnapManager for Hyper-V Description Unable to backup Virtual Machines on newly added Hyper-V Hosts. The new Host added to the Windows Failover Cluster (WFC) and Snap Manager for Hyp...Applies to FlexPod SnapManager for Hyper-V Description Unable to backup Virtual Machines on newly added Hyper-V Hosts. The new Host added to the Windows Failover Cluster (WFC) and Snap Manager for Hyper-V (SMHV) is not visible. Note: This article is applicable only to versions 1.0 through 1.0P2.
SMHV displays Running status wrongly for completed jobs and "_Running.txt" remains
https://kb.netapp.com/Legacy/SnapManager/SMHV_displays_Running_status_wrongly_for_completed_jobs_and_Running_txt_remains
Applies to SnapManager for Hyper-V (SMHV) 2.1.4 Issue SMHV displays Running status for the completed jobs Text file left over with the suffix _Running.txt together with the completed job text file wit...Applies to SnapManager for Hyper-V (SMHV) 2.1.4 Issue SMHV displays Running status for the completed jobs Text file left over with the suffix _Running.txt together with the completed job text file with the suffix _OK.txt under Report Directory Path configured in Report Settings Example: <backup_name>_[job]-ac_[<job_type>]_05-09-2017_00.59.54_OK.txt <backup_name>_[job]-ac_[<job_type>]_05-09-2017_00.59.54_Running.txt
SMHV retention failing to delete snapshots
https://kb.netapp.com/Legacy/SnapManager/SMHV_retention_failing_to_delete_snapshots
SMHV does not apply retention due to the following error seen in the SDW debug log - <snapdrive_installation_path>\SnapDriveDebug.log: P:9424 T:6820 General Critical Error: The credentials for storage...SMHV does not apply retention due to the following error seen in the SDW debug log - <snapdrive_installation_path>\SnapDriveDebug.log: P:9424 T:6820 General Critical Error: The credentials for storage system <SVM_FQDN> are not configured. P:9424 T:6820 General Verbose Response: Details: ID=0, LogLevel=0, SDError=101, Message=Error: The credentials for storage system <SVM_FQDN> are not configured. InnerException : Message : Object reference not set to an instance of an object.
Application consistent backups with SMHV fail to rename snapshot
https://kb.netapp.com/Legacy/SnapManager/Application_consistent_backups_with_SMHV_fail_to_rename_snapshot
01/02-00:00:00.000 PID:9560 TID:7964 filer.cpp@479 An attempt to rename Snapshot copy from '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}_backup' to '<snapshot name_backup' on volume '<volume>' failed on the...01/02-00:00:00.000 PID:9560 TID:7964 filer.cpp@479 An attempt to rename Snapshot copy from '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}_backup' to '<snapshot name_backup' on volume '<volume>' failed on the storage system '<storage system name>'. Error code: 15661.
SMHV backup fails when the clone split load exceeds the maximum
https://kb.netapp.com/Legacy/SnapManager/SMHV_backup_fails_when_the_clone_split_load_exceeds_the_maximum
The shadow copy provider timed out while flushing data to the volume being shadow copied.This is probably due to excessive activity on the volume. 0000001c.017ef16f 41de4afb Wed Jul 01 2020 15:47:00 +...The shadow copy provider timed out while flushing data to the volume being shadow copied.This is probably due to excessive activity on the volume. 0000001c.017ef16f 41de4afb Wed Jul 01 2020 15:47:00 +08:00 [kern_audit:info:1648] 8503e80002dcf6f8 :: YCM-FAS8020: ontapi :: 172.31.40.2:61783 ::SAN-FCP:vsadmin ::Failed to create token for node "FAS8020-01". Reason:Reached maximum split load allowed on the node. :: ONTAPI :: Error
SDW and SMHV GUI become unresponsive at password text boxes
https://kb.netapp.com/Legacy/SnapManager/SDW_and_SMHV_GUI_become_unresponsive_at_password_text_boxes
When using SnapDrive for Windows (SDW) or SnapManager for Hyper-V (SMHV) GUI on Windows Server 2016 via Windows Remote Desktop, the following issues occur at password text boxes. The GUI becomes unres...When using SnapDrive for Windows (SDW) or SnapManager for Hyper-V (SMHV) GUI on Windows Server 2016 via Windows Remote Desktop, the following issues occur at password text boxes. The GUI becomes unresponsive and the following error dialog box can be popped up. To return to MMC and check the status of the snap-in, click Cancel. If you choose to end the snap-in immediately, you will lose any unsaved data. SDW and SMHV have password text boxes in the following windows.
How VM restores are affected if no SnapInfo snapshot is created in SMHV
https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/How_VM_restores_are_affected_if_no_SnapInfo_snapshot_is_created_in_SMHV
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: