2011-04-20 06:20 AM
Everyone, Good morning. We are having a problem with some of our restores. If I select to restore from several specific backups I receive the following error(s):
[09:15:11.434] Getting database backup information from SnapInfo file...
[09:15:11.439] Mounting Snapshot [sqlsnap__wdcsqlutilcn2_04-18-2011_02.00.23__daily] for LUN [J] of Computer [WDCSQLUTILCN2]
[09:15:11.440] SnapManager will use directory [C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint] to mount snapshot [sqlsnap__wdcsqlutilcn2_04-18-2011_02.00.23__daily]
[09:15:11.441] Mount point directory [C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint]
[09:15:11.442] Snapshot will be mounted on subdirectory [MPDisk001]
[09:15:28.943] [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: The request was aborted: Could not create SSL/TLS secure channel..
(SnapDrive Error Code: 0xc00403e3)
[09:15:29.182] *** SNAPMANAGER RESTORE JOB ENDED AT: [04-20-2011 09.15.29]
[09:15:29.184] [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: The request was aborted: Could not create SSL/TLS secure channel..
Any insight is appreciated. Have a nice day!
2011-05-10 02:58 AM
Have you checked if you have not maxed out on number of datastores ?
To increase or change the NFS.MaxVolumes setting open the vSphere Client to the “Hosts and Clusters” view, highlight the ESX host in question, click on the configuration tab, and then under the box labeled “software”, click on “advanced settings”.
We will have to edit the default NFS datastores value if we are going add more than the 8 default datastores. The maximum limit is going to be 64.
2011-05-12 11:10 AM
Hello, the connections are in-tact. The luns were visible. We have rebuilt the environment and are trying again. I believe it was a configuration of the volume(s) that was causing this error. We are not entirely sure yet...
2011-12-07 11:55 AM
this error seems to be a snapdrive related problem with the connectivity to the vCenter.
check SSL connection to the vcenter from the Client and check if you can reach the vcenter via dns (fqdn, short name). also check if the vcenter configuration of snapdrive is accurate and the snapdrive account has enough rights to do what ever it needs to do. the configuration can be read in the actual snapdrive admin guide (6.3.1) page 48 (or html dokumentation - here)
some message popping up:
seems to be more your problem - maybe you can push snapdrive debug log to the forum and one of the netapp guys can descramble it for us...