Failed to Map virtual disk: There are no available SCSI controllers..

[#1]

I keep getting the following errors when trying to verify my SQL backup:

Failed to Map virtual disk: There are no available SCSI controllers..

(SnapDrive Error Code: 0xc00403e3)

Failed with error code 0xc0040814.

The wierd thing is some actually backup but it seems sporadic.

Anyone have any ideas? My Support partner is useless for helping me out with anything...

Thanks. 

[#2]

Hi,

Hope this Article will help you https://kb.netapp.com/support/index?page=content&id=3013601

Thanks

[#3]

Hi Deepuj

Unfortunately the article has not helped me in figuring out why the backups keep failing. The only error that keeps showing up is:

Error code : Failed to create disk in virtual machine, Failed to Map virtual disk: There are no available SCSI controllers..

I am at a loss as to why this is the case, all my LUN's are present?

Why would this error happen?

[#4]

Resized all my discs to double the size. Just in case something strange was happening with the backup size. Still the same error:

[SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: There are no available SCSI controllers..

[#5]

Just deleted all SnapManager info and all jobs. Started from scratch and guess what:

[SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: There are no available SCSI controllers..
(SnapDrive Error Code: 0xc00403e3)

Please can someone shed any light at all?? I am very close in just setting up Backup NFS stores and doing all my backups the traditional and RELIABLE way. Not impressed.

[#6]

I imagine that your SQl is on a virtual server.  Can you give me more info about your environment and is the backup failing or is the verification failing?  How many ESX servers in the group and how disks does it see?

[#7]

Hi Castrojsec 

Only the verification is failing.

SQL 2008 R2 is installed on a Windows server 2008 R2 Enterprise virtual machine. I am using SnapDrive version: 6.5, SnapManager for SQL version: 6.0.1.1431

I have all MDF's and LDF's on LUN's attached to the server via mount points.

I have a LUN snap drive attached where all my snapinfo and Snapmounts go to.

I have 5 hosts in my ESXi 5.1 estate.

Each LUN has a separate backup job.

I hope this helps.

[#8]

Hello,

Do you use SnapManager or SnapProtect, because your post has SnapProtect label in it, but you seem to use SnapManager?

Regards,

JCB

[#9]

Sorry I do not know what 'SnapProtect' is.

I am using SnapDrive version: 6.5, SnapManager for SQL version: 6.0.1.1431

Our Netapp Support partner has said it is not a Netapp issue and to raise the issue with VMware. I have just been on the phone with VMware support who have confirmed it is a Netapp issue and not a VMware issue.  

I am now stuck between a rock and a hard place. 

[#10]

---

YearsleyIT wrote:

Sorry I do not know what 'SnapProtect' is.

I am using SnapDrive version: 6.5, SnapManager for SQL version: 6.0.1.1431

Our Netapp Support partner has said it is not a Netapp issue and to raise the issue with VMware. I have just been on the phone with VMware support who have confirmed it is a Netapp issue and not a VMware issue.  

I am now stuck between a rock and a hard place. 

---

SnaProtect is another backup software which do not require SnapDrive nor SnapManager.

Could you describe your environment?

The SQL servers are virtualized (VMs) ?

For the LUNs, do you use iSCSI or FC?

If it is FC, it is RDM.

if it is iSCSI, is it RDM or do you map the lun in the VM using the Microsoft iSCSI initiator?

Do you encounter the error every time?

Regards,

Jean-Christophe