Skip to main content

Adding Tape Drive with ESX3.5/3i Host

We can add a SCSI controller based Tape Drive with ESX 3.5/3i hosts to connect it with any particular VM to run as Backup Server. According to the HCL, It must be a separate SCSI Adaptor for the Tape drive. After, added the tape drive/SCSI controller, you will see the drive as SCSI device under STORAGE configuration in the VI Client Console. Few LSI will work as well, they must be pure SCSI, not RAID Controllers. Preferable SCSI controller card is Adaptec, However, you can check it on the VMware HCL website before you procure them.
Now, you have to configure this tape drive as a SCSI Device on the particular VM. We add this ESX 3.5 is still using SCSI-2 commands:
Therefore, we need to change the controller Type from LSI Logic to BUS Logic.
1) Shut down the VM and editing its settings.
2) Select to add a new HD - the size of it won't matter as you'll remove it before you save your change
3) On the Advanced Options screen for the Add Hardware wizard, select Virtual Device Node = SCSI(1:0) (or SCSI(2:0) if the VM already have 2 SCSI controllers.
4) Finish the wizard, but don't click OK on the Edit VM settings window. you should see New Hard Disk (adding) and New SCSI Controller (adding).
5) Select the New Hard Disk and click Remove
6) Select the New SCSI Controller and then click Change Type and select Buslogic.
7) Save the change to the VM. You can then edit it again and add the a Generic SCSI device to the buslogic controller (i.e. you'll add it as SCSI(1:x)).
The Device (Target) ID must be identical on the HOST and Virtual Machine. Example: Mine was 2:6:0, I created a SCSI adapter as 1:0:0, and set the tape drive to 1:6:0 (setting device id is important for pass through)
Windows 2008 x64
This version is having problem with Symantec BackupExec, since the Backup application is sending a “scsi split” command to the tape drive on SCSI Passthru, hence ESX causing PSOD error. This has been fixed by this patch: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010135:
Reference:
http://www.vmware.com/pdf/vi35_backup_guide.pdf
http://communities.vmware.com/thread/156068?start=0&tstart=0
http://vikashkumarroy.blogspot.com/2009/04/virtual-machine-as-backup-server.html
http://communities.vmware.com/message/1339072#1339072

Comments

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.

This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager


Creating DSN

Create a System DSN for this d…

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only.

Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address)

~ # /ipmitool lan set 1 vlan id 333

~ # /ipmitool lan print1
Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : 255.255.254.0 MAC Address             : xx:xx:xx…

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk…