Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 12 results
    • https://kb.netapp.com/Legacy/NetApp_HCI/OS/How_to_create_RDM_disks_with_Element_VCP
      Applies to NetApp HCI NetApp Element Plug-In for VMware vCenter (Element VCP) Raw device mapping (RDM) Description This article describes how to provision a volume directly to the virtual machine
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Unable_to_restore_SCSQL_backup_with_RDM_disks
      Applies to SnapCenter Plug-in for SQL (SCSQL) SnapCenter Plugin for VMware vSphere (SCV) SQL DBs on RDM disks Attach/Clone/Restore failing to find an iSCSI initiators, although the connection of the d...Applies to SnapCenter Plug-in for SQL (SCSQL) SnapCenter Plugin for VMware vSphere (SCV) SQL DBs on RDM disks Attach/Clone/Restore failing to find an iSCSI initiators, although the connection of the disks is set to RDM Activity 'Cloning Resources' failed with error: Failed to clone resources, error isMount operation failed with error Failed to mount storage resource, error is None of the host initiators are logged into the controller. Resolution: Please make sure the supplied
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/RDM_provision_fails_with__Failed_to_create_windows_FileSystem
      Applies to SnapCenter Server (SC) 4.3 SnapCenter Plugin For Windows (SCW) 4.3 Issue RDM provision from PowerShell fails with Failed to create windows FileSystem
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SCSQL_clone_refresh_hangs_and_fails_on_connecting_cloned_RDM_LUNs_to_the_Windows_VM
      The clone-refresh seems to be hung for hours, attempting to clone an SQL database to another host. Failed to Map virtual disk: Error Adding Raw Device Mapping -GetLunInformation returned false-<LUN_SE...The clone-refresh seems to be hung for hours, attempting to clone an SQL database to another host. Failed to Map virtual disk: Error Adding Raw Device Mapping -GetLunInformation returned false-<LUN_SERIAL> Later, after the maximum retries has been reached, the removal also fails multiple times: Failed to delete virtual disk: Error Deleting Raw Device Mapping - could not find the Raw Device mapping on ESX Server at VirtualizationAPI.CVirtualServer.UnmapVirtualDisk
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/System_does_not_start_after_reboot_due_to_Unable_to_recover_the_local_database_of_Data_Replication_Module
      EMS log shows: NODE_B:rdb.recovery.failed:EMERGENCY]: Error: Unable to find a master. Unable to recover the local database of Data Replication Module: Management
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Cannot_remove_Windows_plug-in_host_in_SnapCenter
      Applies to SnapCenter Server (SC) SnapCenter Plug-in for Microsoft Windows (SCW) VMware Raw Device Mapping (RDM) Issue Cannot remove Windows plug-in host in SC SQL Plug-in successfully removed from th...Applies to SnapCenter Server (SC) SnapCenter Plug-in for Microsoft Windows (SCW) VMware Raw Device Mapping (RDM) Issue Cannot remove Windows plug-in host in SC SQL Plug-in successfully removed from the SQL host UI error message: Cannot remove the host related objects from the database. This issue might occur if you try to delete multiple hosts at the same time. You must delete one host at a time.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SCSQL_verification_failing_after_successful_backup
      Verification fails at the Query Host Information part of the operation with the error seen in <installation_path>\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_<id>.log: INFO SMCore_7310 PID=[1085...Verification fails at the Query Host Information part of the operation with the error seen in <installation_path>\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_<id>.log: INFO SMCore_7310 PID=[10856] TID=[10] Activity - Query Host Information, Starting INFO SMCore_7310 PID=[10856] TID=[10] Could not get initiator information from host, to mount physical SAN file system(s). ERROR SMCore_7310 PID=[10856] TID=[10] Exception in method: Execute.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_RDM_verification_or_restore_on_Windows_fails_to_find_iSCSI_initiator
      SnapCenter Plug-in for Windows (SCW) 4.x When restoring or verifying SQL Databases, Exchange Mailstores, or Windows Filesystems with RDM usage, the following error is seen: ErrorCode (-1), ErrorMessag...SnapCenter Plug-in for Windows (SCW) 4.x When restoring or verifying SQL Databases, Exchange Mailstores, or Windows Filesystems with RDM usage, the following error is seen: ErrorCode (-1), ErrorMessage (Could not get the iSCSI initiator.) Unable to get the initiator details of host <HOST_FQDN> INFO SMCore_#### PID=[####] TID=[#] Could not get initiator information from host, to mount physical SAN file system(s). System.Exception: Could not get the iSCSI initiator
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SCSQL_restore_fails_with_RDM_disks
      2022-04-13T15:33:29.6579679+02:00 Error SDW PID=[3508] TID=[3476] Error: Failed to get initiator information 2022-04-13T15:33:29.6735986+02:00 Error SDW PID=[3508] TID=[5912] Failed to mount the resou...2022-04-13T15:33:29.6579679+02:00 Error SDW PID=[3508] TID=[3476] Error: Failed to get initiator information 2022-04-13T15:33:29.6735986+02:00 Error SDW PID=[3508] TID=[5912] Failed to mount the resource: <MountPoint> from snapshot: <snapshot_name>. 2022-04-13T15:33:29.6735986+02:00 Error SDW PID=[3508] TID=[5912] Failed to mount the Snapshot copy.Failed to mount the resource: <MountPoint> from snapshot: <snapshot_name>.
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Whatis_the_best_practice_for_RDM_luns_on_NetApp_E-Series_for_VMware_ESXi
      Applies to NetApp E-Series Answer TR-4789: VMware Configuration Guide for E-Series Integration with ESXi VMware express configuration Additional Information
    • https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_-_Is_the_Windows_DSM_required_in_VMware_physical_RDM_deployments
      VMware Physical Raw Device Mappings (pRDM) It is not required to install the E-Series DSM for Windows in VMware environments when deploying physical RDMs (pRDM). VMware ESXi is responsible for managin...VMware Physical Raw Device Mappings (pRDM) It is not required to install the E-Series DSM for Windows in VMware environments when deploying physical RDMs (pRDM). VMware ESXi is responsible for managing the multi-pathing. However installing the DSM inside the Windows guest will not harm anything either. pRDM: Allow the guest operating system to access the hardware directly. vRDM: Allow the virtual machine to use VMware snapshots and other advanced technology.