Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Overland Tape Drive, Adaptec SCSI Card and VMWare ESXi 5.0.0
Hello EE,
I have the following setup:
Dell PowerEdge T610
VMWare ESXi 5.0.0
Windows 2003 Server Standard Ed. 32-bit
Symantec Backup Exec 2012
Adaptec 29320LPE Card (SCSI ID: 0:7)
Overland NEO 200 SCSI Tape Drive (SCSI ID: 0:4)
My goal is to use VMWare to run Backup Exec 2012 and utilize the internal Adaptec 29320LPE SCSI card.
When I boot into Windows, the device manager doesn't see the Adaptec 29320LPE card. I've gone into the Resource Allocation area of the VM, Edit, Hardware tab, show all devices checked, and added a SCSI Device at SCSI ID 0:1 to represent the Adaptec 2932LPE card. SCSI ID 0:7 is not available.
I've gone into the Adaptec SCSI bios and both the SCSI card and tape drive appear at SCSI ID 7 and 0 respectively.
Any suggestions would be appreciated!
Thanks
VMware-Properties.jpg
I have the following setup:
Dell PowerEdge T610
VMWare ESXi 5.0.0
Windows 2003 Server Standard Ed. 32-bit
Symantec Backup Exec 2012
Adaptec 29320LPE Card (SCSI ID: 0:7)
Overland NEO 200 SCSI Tape Drive (SCSI ID: 0:4)
My goal is to use VMWare to run Backup Exec 2012 and utilize the internal Adaptec 29320LPE SCSI card.
When I boot into Windows, the device manager doesn't see the Adaptec 29320LPE card. I've gone into the Resource Allocation area of the VM, Edit, Hardware tab, show all devices checked, and added a SCSI Device at SCSI ID 0:1 to represent the Adaptec 2932LPE card. SCSI ID 0:7 is not available.
I've gone into the Adaptec SCSI bios and both the SCSI card and tape drive appear at SCSI ID 7 and 0 respectively.
Any suggestions would be appreciated!
Thanks
VMware-Properties.jpg
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Unfortunately, I've some bad news for you.
Tape Drives are tempermental under ESXi 4.x and 5.0, the best way to try and get them to work, is to install a dedicated SCSI controller in the host, and use VM Direct Path to present the PCI card to the VM, connect the tape drive to the SCSI card.
This is the approved and supported method by Overland and Symantec.
Note: VMware does not support Tape Drives connected directly to ESXi 5.0 which is documented under Release Notes for vSphere 5.0.
Source
http://kb.vmware.com/kb/1016407
Tape Drives are tempermental under ESXi 4.x and 5.0, the best way to try and get them to work, is to install a dedicated SCSI controller in the host, and use VM Direct Path to present the PCI card to the VM, connect the tape drive to the SCSI card.
This is the approved and supported method by Overland and Symantec.
Note: VMware does not support Tape Drives connected directly to ESXi 5.0 which is documented under Release Notes for vSphere 5.0.
Source
http://kb.vmware.com/kb/1016407
You need to install the Backup Tape Drive drivers and run abackup from Windows wit Backup Exec.
This technote should help
http://www.symantec.com/business/support/index?page=content&id=TECH17931
This technote should help
http://www.symantec.com/business/support/index?page=content&id=TECH17931
Hi Hanccocka,
Based on your comments, I thought I had a dedicated SCSI controller card installed with the tape drive connected to the card. The only thing I think I'm missing is the VM Direct Path portion. Is VM Direct Path an add-on to VMWare or is it built into it already? If so, where can I find it?
Hi TG-TIS,
I think I need to address at least getting Windows Server to recognize the SCSI card before I can install the tape drive drivers, correct?
Thanks!
Based on your comments, I thought I had a dedicated SCSI controller card installed with the tape drive connected to the card. The only thing I think I'm missing is the VM Direct Path portion. Is VM Direct Path an add-on to VMWare or is it built into it already? If so, where can I find it?
Hi TG-TIS,
I think I need to address at least getting Windows Server to recognize the SCSI card before I can install the tape drive drivers, correct?
Thanks!
see here how to setup its included with ESXi 5.0, yes you need to get this working first in the VM.
http://www.petri.co.il/vmware-esxi4-vmdirectpath.htm
http://www.petri.co.il/vmware-esxi4-vmdirectpath.htm
Yes, however Backup Exec does not use the drivers that comes from the tape manufacturer. Backup Exec only uses it's own tape drivers.
I've install multiple tape drives and scsi adaptors for Backup Exec. The existing tape drive drivers needs to be uninstalled and then execute aa application called Tapeinst.exe that installed the BE tape driver drivers
http://www.symantec.com/business/support/index?page=content&id=TECH6098
.
I've install multiple tape drives and scsi adaptors for Backup Exec. The existing tape drive drivers needs to be uninstalled and then execute aa application called Tapeinst.exe that installed the BE tape driver drivers
http://www.symantec.com/business/support/index?page=content&id=TECH6098
.
Hi hanccocka,
I went through the link you provided and was able to get the SCSI card to be enabled in the passthrough section. I reboot the VM Server and the green light was on the SCSI card.
I went to add the card to the VM and when I selected SCSI Device, the only two things that came up were CD\DVD and Unknown DP. I selected Unknown DP and assigned it to SCSI (0:1) SCSI device 1.
I'm sure that is incorrect as Windows still doesn't see the device. Prior to all of this, I went into the BIOS of the server itself and turned on VT as it was disabled.
Any suggestions?
Thanks
I went through the link you provided and was able to get the SCSI card to be enabled in the passthrough section. I reboot the VM Server and the green light was on the SCSI card.
I went to add the card to the VM and when I selected SCSI Device, the only two things that came up were CD\DVD and Unknown DP. I selected Unknown DP and assigned it to SCSI (0:1) SCSI device 1.
I'm sure that is incorrect as Windows still doesn't see the device. Prior to all of this, I went into the BIOS of the server itself and turned on VT as it was disabled.
Any suggestions?
Thanks
Hi TG-TIS,
I opened BE 2012 but I don't have "Tools, Wizards" options. I tried to find where I could toggle between what I have and what the document says to do, but was unable to do so. I ran the "tapeinst.exe" file and picked up at Figure 4.
I uninstalled the drivers and rebooted. I ran tapeinst.exe again and followed the directions only to be shown that the device was not detected. Please see attachment.
Thanks
BE-Hardware-Scan.jpg
Backup-Exec.jpg
I opened BE 2012 but I don't have "Tools, Wizards" options. I tried to find where I could toggle between what I have and what the document says to do, but was unable to do so. I ran the "tapeinst.exe" file and picked up at Figure 4.
I uninstalled the drivers and rebooted. I ran tapeinst.exe again and followed the directions only to be shown that the device was not detected. Please see attachment.
Thanks
BE-Hardware-Scan.jpg
Backup-Exec.jpg
once the card is added to the VM, just treat the VM as a physical server.
did the VM install the drivers for the SCSI card?
do not add a separate scsi device to the VM this is scsi passthrough and not VM Direct Path.
did the VM install the drivers for the SCSI card?
do not add a separate scsi device to the VM this is scsi passthrough and not VM Direct Path.
Hi hanccocka,
Ok, I did as you suggested and treated the VM as a physical server. I did NOT add it to the VM as a new SCSI device. I just left it in the passthrough area with the green light on it.
I booted into my VM and Windows didn't see the card. Any other suggestions? I feel like I'm close, but no cigar :\
Thanks
Ok, I did as you suggested and treated the VM as a physical server. I did NOT add it to the VM as a new SCSI device. I just left it in the passthrough area with the green light on it.
I booted into my VM and Windows didn't see the card. Any other suggestions? I feel like I'm close, but no cigar :\
Thanks
One additional thing I just noticed...I went to device manager and selected to show hidden devices and noted that "vmscsi" had issues. Please see attached.
Thanks
vmscsi-error.jpg
Thanks
vmscsi-error.jpg
I did play with adding a SCSI device to the VM. I removed it and that error went away. Good call :)
Now, back to not being able to see the card in Windows. Any thoughts there?
Thanks
Now, back to not being able to see the card in Windows. Any thoughts there?
Thanks
NO SCSCI
YOU ATE NOT USING SCSI PASSTHROUGH DIFFERENT TECHNOLOGY.
YOU ARE TRYING TO USE VM DIRECT PATH
TWO VERY DIFFERENT TECHNOLOGIES
HAVE YOU ADDED A PCI CARD DEVICE TO THE VM?
YOU ATE NOT USING SCSI PASSTHROUGH DIFFERENT TECHNOLOGY.
YOU ARE TRYING TO USE VM DIRECT PATH
TWO VERY DIFFERENT TECHNOLOGIES
HAVE YOU ADDED A PCI CARD DEVICE TO THE VM?
Are you yelling at me with all CAPS? LOL
I am using Passthrough, not direct path. There are NO PCI Card devices in the VM. See attached.
Thanks
VMware-No-PCI.jpg
I am using Passthrough, not direct path. There are NO PCI Card devices in the VM. See attached.
Thanks
VMware-No-PCI.jpg
Yes, CAPS intentional!
SCSI Passthrough is not recommended and does not work reliable or supported.
It's not recommended by Overland, Symantec Backup Exec, their recommeded option is VM Direct Path. (as I mentioned in opening response!).
A VM with dedicated PCI (SCSI CARD) added using VM Direct Path, and this is also crap!
and does not work reliably!
hence, why ALL our customers abanonded tape with ESXi!
SCSI Passthrough is not recommended and does not work reliable or supported.
It's not recommended by Overland, Symantec Backup Exec, their recommeded option is VM Direct Path. (as I mentioned in opening response!).
A VM with dedicated PCI (SCSI CARD) added using VM Direct Path, and this is also crap!
and does not work reliably!
hence, why ALL our customers abanonded tape with ESXi!
You know hanccocka, people use this service for help. Perhaps I'm not as technically saavy as you, that's why I use this service. Excuse me for not completely grasping everything you have had to say. If you are so easily irritated by people like me, perhaps you should reconsider assisting people in this forum.
If there is anyone else out there willing to assist without an attitude, I would appreciate your help.
Thanks
If there is anyone else out there willing to assist without an attitude, I would appreciate your help.
Thanks
Sorry, if it comes across that way, but Tape Support is difficult with ESXi. There is no easy solution, hence why VMware stopped supporting it!
Tape Backups are not supported by VMware, and passed it to the vendor. They found the best chance of working was VM Direct Path.
Passthrough the PCI card, add to the VM, and then treat as Physical Machine from their on.
Recommended Option is VM Direct Path.
SCSI Passthrough unreliable.
It's all unreliable, but VM Direct Path is your best chance of a working solution.
Tape Backups are not supported by VMware, and passed it to the vendor. They found the best chance of working was VM Direct Path.
Passthrough the PCI card, add to the VM, and then treat as Physical Machine from their on.
Recommended Option is VM Direct Path.
SCSI Passthrough unreliable.
It's all unreliable, but VM Direct Path is your best chance of a working solution.
Okay, I've re-read all youre comments again.
and I think I know, which bit you are missing here.
Once, you have added the PCI SCSI card using VM Direct Path which you have completed.
You then also need to Edit the VM Settings (Right Click VM, Edit Settings), and add a PCI Device, in my example it states unavailable because I've not added a SCSI card via VM Direct Path.
But on your server, you should be able to add this SCSI card added previously in VM Direct Path to your VM.
Once you have this VM communicating directly with the SCSI card in VM Direct Path I/O mode, hopefully Windows will plug and play and install drivers for this SCSI card, and then you should be on the route for Detection with Tape Drive.
This is the recommended method, but I may add it's supported by Vendors, Symantec and Overland not VMware, and still has issues.
Unfortunalteltly, this may not be the result you desire, but I'm still trying to help you with your solution, although it may not work.
and I think I know, which bit you are missing here.
Once, you have added the PCI SCSI card using VM Direct Path which you have completed.
You then also need to Edit the VM Settings (Right Click VM, Edit Settings), and add a PCI Device, in my example it states unavailable because I've not added a SCSI card via VM Direct Path.
But on your server, you should be able to add this SCSI card added previously in VM Direct Path to your VM.
Once you have this VM communicating directly with the SCSI card in VM Direct Path I/O mode, hopefully Windows will plug and play and install drivers for this SCSI card, and then you should be on the route for Detection with Tape Drive.
This is the recommended method, but I may add it's supported by Vendors, Symantec and Overland not VMware, and still has issues.
Unfortunalteltly, this may not be the result you desire, but I'm still trying to help you with your solution, although it may not work.
I realize it is difficult...that is why I'm here :) I have a Dell PowerEdge T610 server but I'm not sure if it supports VM Direct Path. How can I tell? I will use whatever it takes to make this work...
Ok, you are suggesting to me to use VM Direct Path. From what I've read on the links, I would
Click Configuration > Storage Adapters.
On the Storage Adapters list, identify the controller that has the tape attached. In my case that would be vmhba2 - AHA-29320ALP (See attached)
Under Details, the Runtime Name of the tape device is vmhba2:C0:T4:L0
I selected the virtual machine that use the tape device, and click Summary > Edit Settings.
Click Hardware > Add.
Select SCSI Device from the list of device types and click Next.
I'm supposed to select the appropriate device from the SCSI Device drop down menu. Unfortunately, it is not listed. I only get CD/DVD HL-DT-ST or Unknown DP. (See attached)
This is where I get stuck. I want to believe that the card should show up in the SCSI Device drop down from the previous step.
Does that make sense?
Thanks
vmware---vmhba2.jpg
vmware---no-scsi.jpg
Ok, you are suggesting to me to use VM Direct Path. From what I've read on the links, I would
Click Configuration > Storage Adapters.
On the Storage Adapters list, identify the controller that has the tape attached. In my case that would be vmhba2 - AHA-29320ALP (See attached)
Under Details, the Runtime Name of the tape device is vmhba2:C0:T4:L0
I selected the virtual machine that use the tape device, and click Summary > Edit Settings.
Click Hardware > Add.
Select SCSI Device from the list of device types and click Next.
I'm supposed to select the appropriate device from the SCSI Device drop down menu. Unfortunately, it is not listed. I only get CD/DVD HL-DT-ST or Unknown DP. (See attached)
This is where I get stuck. I want to believe that the card should show up in the SCSI Device drop down from the previous step.
Does that make sense?
Thanks
vmware---vmhba2.jpg
vmware---no-scsi.jpg
Okay, let's get on with trying to solve the technical issues at hand, thanks for sticking with us. It was not my intentions to offend, sorry, if it came across that way.
let me have a read and look at screenshots.
let me have a read and look at screenshots.
It's cool hanccocka...frustration on both sides :) Apology accepted! Looking forward to your findings.
Thanks
Thanks
Okay, I've had a quick look at the VMware Hardware Compatibility List, and it suggests the T610 is not compatible with VM Direct Path.
Argh...so nothing else you can think of then...bummer. Well, sorry I wasted your time with this but thanks for trying.
If I enable passthrough it shows it as an active device with the green "on" button. Is that what you mean?
So when you selected the Host, Configuration, Advanced Settings, you were able to Add the Card.
Can you screenshot it?
Can you screenshot it?
Okay, well that's fantastic news. VMware Hardware Compatibility List is WRONG!
Okay, lets proceed to next steps.
You will need to Power off the VM.
Right Click Edit Settings:- Click Add and select PCI Device, followed By Next
and select AHA-29320ALP, from the drop down, Next and Finish.
Power Up VM.
Windows should Plug and Play and Add the Drivers automatically.
You should be able to confirm, by selecting Device Manager, and check Under SCSI Controllers.
Okay, lets proceed to next steps.
You will need to Power off the VM.
Right Click Edit Settings:- Click Add and select PCI Device, followed By Next
and select AHA-29320ALP, from the drop down, Next and Finish.
Power Up VM.
Windows should Plug and Play and Add the Drivers automatically.
You should be able to confirm, by selecting Device Manager, and check Under SCSI Controllers.
That all sounds correct in my opinion, however, PCI Device is not an option for selection.
I've attached a pic of the mobo, Adaptec card and a screenshot of the Edit settings, Add hardware section. It's like VM Server sees the card, but the VM doesn't.
VMWare---No-PCI.jpg
VMWare---T610-Mobo.jpg
VMware---Adaptec-card.jpg
I've attached a pic of the mobo, Adaptec card and a screenshot of the Edit settings, Add hardware section. It's like VM Server sees the card, but the VM doesn't.
VMWare---No-PCI.jpg
VMWare---T610-Mobo.jpg
VMware---Adaptec-card.jpg
ah, okay, this is because you are running a Virtual Machine version 4.0 and not 7.0, 7.0 is required for PCI.
Do you have an option which states Upgrade Virtual Machine Hardware?
(do not continue).
Are you VMware Tools Update to Date? e.g. it does not state out of date tools?
Do you have an option which states Upgrade Virtual Machine Hardware?
(do not continue).
Are you VMware Tools Update to Date? e.g. it does not state out of date tools?
You need to Right Click Virtual Machine and Check if the Option ot Upgrade Virtual Machine hardware is present.
Okay, ensure VMware Tools are up to date, and Click Upgrade Virtual Machine hardware.
You may have to re-start the VM to check, you do not get Out of Date VMware Tools, it's important tools is updated before Virtual Machine Hardware.
You may have to re-start the VM to check, you do not get Out of Date VMware Tools, it's important tools is updated before Virtual Machine Hardware.
Ok, the "Update Tools" button was not available so I'm assuming they are up to date. Unfortunately, after running the Virtual Machine Hardware I received the following error:
Failed to power on VM.
Could not power on VM : Admission check failed for memory resource See the VMware ESX Resource Management Guide for information on resource management settings.
Group vm.3683: Invalid memory allocation parameters for VM vmm0:ALOTN-SRV03. (min: 1048576, max: -1, minLimit: -1, shares: -3, units: pages)
Group vm.3683: Cannot admit VM: Memory admission check failed. Requested reservation: 1066779 pages
It just keeps getting better! :(
Thanks
Failed to power on VM.
Could not power on VM : Admission check failed for memory resource See the VMware ESX Resource Management Guide for information on resource management settings.
Group vm.3683: Invalid memory allocation parameters for VM vmm0:ALOTN-SRV03. (min: 1048576, max: -1, minLimit: -1, shares: -3, units: pages)
Group vm.3683: Cannot admit VM: Memory admission check failed. Requested reservation: 1066779 pages
It just keeps getting better! :(
Thanks
check cpu and memory for the VM.
Also check the resources tab, and reduce the sliders for memory and cpu tomzero.
Also check the resources tab, and reduce the sliders for memory and cpu tomzero.
I've left it at '0' and also tried making the memory reservation to equal 6136.
Module MemSched power on failed.
An error occurred while parsing scheduler-specific configuration parameters.
Invalid memory setting for FPT: memory reservation (sched.mem.min) should be equal to memsize(6136)
Module MemSched power on failed.
An error occurred while parsing scheduler-specific configuration parameters.
Invalid memory setting for FPT: memory reservation (sched.mem.min) should be equal to memsize(6136)
okay, this is the issue 6GB host, with 6GB VM?
not enough Host Memory, you will need to reduce the ram in the VM.
not enough Host Memory, you will need to reduce the ram in the VM.
I've got two areas where memory appears...
VM Edit Settings
--> Hardware Tab (Shows Memory at 2048MB)
--> Resources (Shows CPU at '0' both for Reservation and Limit with "Unlimited" NOT checked)
--> Resources (Shows Memory at '0' with "Shares" set to "Normal" and 20480 grayed out)
--> Resources (Shows '0' for both Reservation and Limit with "Unlimited" NOT checked)
VMware---Hardware.jpg
VMware---Resources.jpg
VM Edit Settings
--> Hardware Tab (Shows Memory at 2048MB)
--> Resources (Shows CPU at '0' both for Reservation and Limit with "Unlimited" NOT checked)
--> Resources (Shows Memory at '0' with "Shares" set to "Normal" and 20480 grayed out)
--> Resources (Shows '0' for both Reservation and Limit with "Unlimited" NOT checked)
VMware---Hardware.jpg
VMware---Resources.jpg
It seems that regardless of where I set the memory (low or high), I get the same error that adjusts to the amount of memory I've designated. For example:
Module MemSched power on failed.
An error occurred while parsing scheduler-specific configuration parameters.
Invalid memory setting for FPT: memory reservation (sched.mem.min) should be equal to memsize(2048)
Module MemSched power on failed.
An error occurred while parsing scheduler-specific configuration parameters.
Invalid memory setting for FPT: memory reservation (sched.mem.min) should be equal to memsize(2048)
Adding a VMDirectPath device to a virtual machine sets memory reservation to the memory size of the virtual machine.
e.g 2GB
was it at 2GB previosuly?
remove the PCI device, and check it VM starts
e.g 2GB
was it at 2GB previosuly?
remove the PCI device, and check it VM starts
Yes, with a PCI Device the Reservation Must be equal to memory in the VM.
e.g. 2GB
was it 6GB before? because if the VM was 6GB and Reservawtion 6GB, and host only had 6GB, not enough memory (with overhead to start VM)
e.g. 2GB
was it 6GB before? because if the VM was 6GB and Reservawtion 6GB, and host only had 6GB, not enough memory (with overhead to start VM)
Original memory allocation was 4096MB. After removing the PCI Device, the VM booted up without a problem.
Okay, so we've not broke the VM.
(just an aside, adding lots of processors in the VM, e.g. 4 vCPU may not be a good idea, because vSMP can slow a VM down, if the VM cannot take advantage of the vCPU, e.g. SQL or Exchange, it's best to allocate a single vCPU, and add another if you require additional performance). Moving on...
do you have any other VMs on this host?
and the host only has 6GB?
when you add a PCI device a reservation must equal memory in the VM, if that memory is not available to the VM, at power on, this is the reason for the error.
because reserved memory is ring fenched and stolen from the host for this VM.
when memory is not reserved, your VM will start, but it will be using 4GB, when reserved it will be!
(just an aside, adding lots of processors in the VM, e.g. 4 vCPU may not be a good idea, because vSMP can slow a VM down, if the VM cannot take advantage of the vCPU, e.g. SQL or Exchange, it's best to allocate a single vCPU, and add another if you require additional performance). Moving on...
do you have any other VMs on this host?
and the host only has 6GB?
when you add a PCI device a reservation must equal memory in the VM, if that memory is not available to the VM, at power on, this is the reason for the error.
because reserved memory is ring fenched and stolen from the host for this VM.
when memory is not reserved, your VM will start, but it will be using 4GB, when reserved it will be!
the VMware Kb articles are here
http://kb.vmware.com/kb/1018180
http://kb.vmware.com/kb/2002779
and if you set a reservation to 4096, does it fail at power-on?
http://kb.vmware.com/kb/1018180
http://kb.vmware.com/kb/2002779
and if you set a reservation to 4096, does it fail at power-on?
I think the problem was the order of things. I had the VMServer with 6GB and the VM with 6GB. After removing the PCI from the VM and THEN reducing the memory to 2048MB and THEN readding the PCI, it allowed me to boot to the desktop.
So, you suggest I reduce the number of PROCs to 1 and bump the memory up to 4096?
Checking now to see if the card is in device manager.
So, you suggest I reduce the number of PROCs to 1 and bump the memory up to 4096?
Checking now to see if the card is in device manager.
I would certainly start low (vCPU = 1) and Memory Low and increase if required.
What is the VMs role?
What is the VMs role?
hanccocka! You're the man!!! Even the tape drive is showing up as being there but no drivers installed.
I've learned more from you today than I have in the last two weeks trying to figure this out on my own.
Thanks so much for your patience with me and this issue. Made my day!
VMware---Hardware-is-there.jpg
I've learned more from you today than I have in the last two weeks trying to figure this out on my own.
Thanks so much for your patience with me and this issue. Made my day!
VMware---Hardware-is-there.jpg
A Pleasure, this is what we Experts do on EE! (as Volunteers!)
This is the recommended method of adding a tape drive to ESXi 5.0 (although not supported by VMware).
This is the supported method Overland and Symantec will recommend.
BUT, be warned strange things can happen still, and for those issues with Backup software you will need to possibly raise with Symantec or Overland.
and Virtual Server using VM Direct Path is a different beast to a Physical Machine with a Tape Drive connected.
This is the recommended method of adding a tape drive to ESXi 5.0 (although not supported by VMware).
This is the supported method Overland and Symantec will recommend.
BUT, be warned strange things can happen still, and for those issues with Backup software you will need to possibly raise with Symantec or Overland.
and Virtual Server using VM Direct Path is a different beast to a Physical Machine with a Tape Drive connected.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial