Applies to SME/SMSQL 7.1/7.2 or SMHV 2.X SnapDrive 7.0.3 or 7.1.x FlexPod SnapManager for HyperV SnapManager for Microsoft SQL Server Issue SMSQL and SnapMirror XDP integration: quick set up guide and...Applies to SME/SMSQL 7.1/7.2 or SMHV 2.X SnapDrive 7.0.3 or 7.1.x FlexPod SnapManager for HyperV SnapManager for Microsoft SQL Server Issue SMSQL and SnapMirror XDP integration: quick set up guide and possible reasons for SnapManager to show the 'Archive backup to Secondary Storage' check box as disabled.
Applies to SnapManager for Exchange (200+) SnapManager for Microsoft SQL Server After adjusting the HBA queue depth on a QLogic HBA on a Windows 2003 Host, a performance monitoring tool such as Perfmo...Applies to SnapManager for Exchange (200+) SnapManager for Microsoft SQL Server After adjusting the HBA queue depth on a QLogic HBA on a Windows 2003 Host, a performance monitoring tool such as Perfmon for Windows reveals that input/output (I/O) from the host to the filer improved on a per HBA basis, but not on a per LUN basis. After further research: Applications are confirmed to be functioning properly. Filer shows no performance bottlenecks. SAN fabric shows no performance bottlenecks.
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 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."
SnapManager for Hyper-V, Exchange, or SQL might not correctly be able to create snapshots with a SnapMirror label and they might not show the Archive Backup option in the Backup and Verify option. The...SnapManager for Hyper-V, Exchange, or SQL might not correctly be able to create snapshots with a SnapMirror label and they might not show the Archive Backup option in the Backup and Verify option. The above symptom manifests itself even though the local backups are working fine and the SnapMirror policy on the destination is configured correctly, according to the following article:
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
Backup fails with error in the SMSQL job report: Error : Failed to create snapshot [<instance_name> : admin]. Error Details: [SnapDrive Error]: SnapDrive was unable to create a Snapshot copy of one or...Backup fails with error in the SMSQL job report: Error : Failed to create snapshot [<instance_name> : admin]. Error Details: [SnapDrive Error]: SnapDrive was unable to create a Snapshot copy of one or more LUNs that reside on different storage system volumes. All Snapshot copies that were created as part of this LUN Snapshot copy operation were deleted. Failed to create snapshot of volume <volume_name> reason: cannot exceed maximum number of snapshot copies
