vmfs

Veeam Backup and Fast SCP Error

You get an error after attempting to backup a vm, which is similar to the following…

opening `/vmfs/volumes/48ef3738-77af8bc0-d6aa-0022190bdb5f/vm_name/vm_name.vmdk’: Permission denied

The issue is that the “Service Console Agent Mode” is being used, and there is a permission problem preventing a proper backup.

The work-around is as follows… Uncheck “Use Service Console Connection” check box on the page where you specified credentials, this will make Veeam fall back to agentless mode and use SOAP Credentials.

NS

ESX 3.5, IDE, and Me

What the heck am I talking about you say? Well I decided to load ESX 3.5 on a workstation of mine. This is so I could do a test upgrade from 3.5 to 3.5 Patch 3, mainly because I want to make sure VMFS and the VMs are retained after upgrading to said patch level.

So I commenced installing ESX 3.5 on my 40GB IDE drive, yeah I said IDE, who uses those anymore anyways, apparently I do. The install went fine, for the most part, until it said that I wouldn’t be able to use the current drive as a datastore (without advanced configuration). Anyways on I go, I finish the install and all is fine. I was able to connect using Virtual Infrastructure Client, but then I see the message that ViC could not find any static storage, click here to configure a datastore. I clicked on the link and of course nothing was there… did some searching and it turns out that ESX 3.5 does not support IDE drives as a datastore due to the fact that NCQ(native command queuing) is missing from IDE Drive, however SATA drives will work fine. So what I ended up doing is I just installed a 80GB Sata drive, yes small i know, but its only for testing purposes, and rebooted the ESX machine, from ViC. Upon rebooting it found the new hardware and I was able to use ViC to add the new datastore… all 80GBs of it, all right!

Moral of the story… SATA/SCSI okay, IDE not okay

Till next time,

NS

VMFS and Block Sizes

Well i ran into this error today (4:30 am CST, don’t ask me why I am up right now!) “File too large” when trying to create a virtual machine with a 30GB drive and a 300GB drive. I tracked it down to the fact that the block size on my second LUN is 1MB which gives a max file size of 256GB. I will have to change the block size to 2MB which will let me create 512GB files, unfortunately I need to move a couple VMs off there to do so, I will just end up utilizing vmotion to move the VMs then reformat the LUN using a 2MB block size, then vmotion back. Sounds like fun! Well it isn’t, but its an interesting learning experience. Don’t make the same mistake, and you wont have to deal with this issue yourself.

The table below is the Block size in correspondence with the max file size

1MB Block Size: Maximum filesize = 256GB
2MB Block Size: Maximum filesize = 512GB
4MB Block Size: Maximum filesize = 1024GB
8MB Block Size: Maximum filesize = 2048GB

NS