What NTFS allocation unit size (also called cluster size, or block size) should be used when creating or formatting Logical Unit Number (LUNs) for Microsoft SQL Server and Microsoft Exchange? Sequenti...What NTFS allocation unit size (also called cluster size, or block size) should be used when creating or formatting Logical Unit Number (LUNs) for Microsoft SQL Server and Microsoft Exchange? Sequential Read and Write Test (transfer size = 64KB) - the differences between the allocation unit sizes of 4K and 64K are 4% for sequential reads and less than 1% for sequential writes.
Applies to SnapDrive for Windows (SDW) ONTAP 9.3 Microsoft Windows Server Family Issue Virtual Machine running with Windows 2016 can't create Snapshots on the LUNs Error: SD-00003: Error creating snap...Applies to SnapDrive for Windows (SDW) ONTAP 9.3 Microsoft Windows Server Family Issue Virtual Machine running with Windows 2016 can't create Snapshots on the LUNs Error: SD-00003: Error creating snapshot: SD-10016: Error executing snapdrive command "snap create": Failed to create a consistent Snapshot copy of one or more LUN(s).
SnapDrive loses Transport Protocol Settings after reboot if the SVM management LIF is unreachable. The following error message is reported in the Snpdrvdbg.log: Or the following error message can be s...SnapDrive loses Transport Protocol Settings after reboot if the SVM management LIF is unreachable. The following error message is reported in the Snpdrvdbg.log: Or the following error message can be seen, if RPC default is active, also in the SnpDrvDbg.log: Unable to get filer version for '<SVM>'. Error: RPC Error - The RPC server is unavailable. Failed to get Data ONTAP version running on the storage system <SVM> as it is not reachable.
When there is a Metrocluster Switchover, SnapDrive looks for the credentials for the surviving SVM, typycally if svm is called svm1, the surviving svm will be svm-mc. Somehow this only happens during ...When there is a Metrocluster Switchover, SnapDrive looks for the credentials for the surviving SVM, typycally if svm is called svm1, the surviving svm will be svm-mc. Somehow this only happens during SME (SnapManager for Exchange) verification process: we have observed the issue so far only when performing remote backup and verification, not local, but you can't exclude that we may see the issue in other circusmtances.
Applies to SnapDrive for Windows (SDW) 7.1.5 Microsoft Windows Failover Cluster Issue Trying to connect LUN getting access is denied in SnapDrive SDW UI error: VDI disk object for the LUN s/n '<lun_id...Applies to SnapDrive for Windows (SDW) 7.1.5 Microsoft Windows Failover Cluster Issue Trying to connect LUN getting access is denied in SnapDrive SDW UI error: VDI disk object for the LUN s/n '<lun_id>' has not being found
Applies to Windows Server 2008 and above SnapDrive or SnapManager iSCSI 7MTT Issue Post performing 7MTT migration, disks in Windows Disk Management windows shows as "Unallocated"
Applies to SDU failed to discover storage resources, leading to SnapManager failures showing the following error. SD-10016: Error executing snapdrive command "/usr/sbin/snapdrive storage show -all": 0...Applies to SDU failed to discover storage resources, leading to SnapManager failures showing the following error. SD-10016: Error executing snapdrive command "/usr/sbin/snapdrive storage show -all": 0001-185 Command error: storage show failed: no NETAPP devices to show or add the host to the trusted hosts (options trusted.hosts) on the storage system or retry after changing snapdrive.conf to use https for storage system communication and restarting snapdrive daemon.
Applies to SnapManager for SQL (SMSQL) 7.2.3 SnapDrive for Windows (SDW) 7.1.5 Issue Backup randomly fails with error seen in the job report "Failed to establish connection to net.tcp://SG1PEVLTD22:80...Applies to SnapManager for SQL (SMSQL) 7.2.3 SnapDrive for Windows (SDW) 7.1.5 Issue Backup randomly fails with error seen in the job report "Failed to establish connection to net.tcp://SG1PEVLTD22:808/SnapDrive/StorageResolution."
Applies to SnapCenter Issue An exception like the following example appears in SnapDriveSALDebug.log of SnapCenter on Windows host: Verbose SAL PID=[3628] TID=[5164] scope: \\SNAPCTR\root\MSCluster Ve...Applies to SnapCenter Issue An exception like the following example appears in SnapDriveSALDebug.log of SnapCenter on Windows host: Verbose SAL PID=[3628] TID=[5164] scope: \\SNAPCTR\root\MSCluster Verbose SAL PID=[3628] TID=[5164] WMI query 'SELECT * FROM MSCLUSTER_CLUSTER' threw exception 'Invalid namespace '. Config is not a cluster.
[19:00:16.312] [SERVER_NAME] Database requested has not been configured for backup. This database is marked as:Disk(s) used by this database are used by other database(s).. Server:SERVER_NAMEINSTANCE ...[19:00:16.312] [SERVER_NAME] Database requested has not been configured for backup. This database is marked as:Disk(s) used by this database are used by other database(s).. Server:SERVER_NAMEINSTANCE Database:DATABASE_NAME This Database will be skipped. [19:00:16.152] [SERVER_NAME] Failed to Get SnapInfo Directory from Registry [19:00:16.152] [SERVER_NAME] [19:00:16.152] [SERVER_NAME] Deletion of the oldest backup sets does not proceed, as there is an error during backup of this database.
