Veeam – Error when launching the console – SQL server is not available

This is a really short post about a problem which is actually not a problem. Today I’ve worked at a customer site where the Veeam Backup & Replication (v7.0) database was located on a remote SQL server.

When I was logged in as local Administrator, I always was prompted with the following error message when launching the console:


The next step was to check the Veeam registry values which seemed to be fine:

HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlDatabaseName
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlInstanceName
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlServerName

Then I saw that the user configured to start the Veeam services was a Active Directory service account which actually had proper privileges on the remote DB. After checking the application event log on the SQL server I realized that every time I’ve tried to launch the console, the local Administrator of the backup server attempted to log in which of course got denied.

After logging in (on the backup server) with the service account the console started as usual. So it seems that the console opens a SQL connection to retrieve all the configuration information and since this happens within the corresponding context of the logged in user, the account requires proper privileges on the Veeam DB.

I hope this helps you to save some time!

DataCore SANsymphony-V – Modify vDisk access using PowerShell

Today two colleagues of mine wanted to set the storage access for a backup server to read only for ALL vDisks. Going through all virtual disks manually to set every path to read-only would be really cumbersome so they have used PowerShell instead. So all credits go to them, thanks!

I thought it was worth sharing the simple scripts since it can be really handy:

Get-DcsVirtualLogicalUnit | where {$_.caption -like “*<HOSTNAME>*“} | Set-DcsVirtualLogicalUnitProperties -Access “ReadOnly”
The script uses the caption field of the Get-DcsVirtualLogicalUnit cmlet to determine the the host for which the access should be modified. Please note that this will change the read-write access to read-only for ALL vDisks!

You can use the following script to verify if the access has been changed successfully:

foreach ($path in ( Get-DcsVirtualLogicalUnit | where {$_.caption -like “*<HOSTNAME>*”})) { echo $path.caption $path.access} foreach ($path in ( Get-DcsVirtualLogicalUnit | where {$_.caption -notlike “*<HOSTNAME>*”})) { echo  $path.access}

VMware ESXi – async drivers

Recently we got some storage problems with a couple of ESXi hosts and one of the recommendations of the VMware support was to update the async drivers. I think that there isn’t much awareness about those drivers as it actually should be, that’s why I wrote this short post.

Async drivers are developed by partners like QLogic and certified by VMware to optimally support their hardware. A good example is the pretty common Fibre Channel HBA QLE2562.

A certain version of those drivers will be shipped with the VMware ESXi image or the corresponding OEM images. As you probably can imagine that those drivers updated more often than the ESXi images. An example of which QLogic drivers are included in the VMware ESXi images can be found here: Default QLogic HBA driver/firmware versions for ESXi

OEMs like Dell will probably include more recent drivers for their hardware when they release an updated version of the image like the following:

Dell – VMware ESXi 5.1 Update 2 Recovery Image

VMware ESXi 5.5 Image Dell customized ISO

In case of the Dell images it’s recommended to take a look at the “Important Information” section on the Dell download site to check which drivers are really included:

Qlogic HBA Drivers & its versions(Available at ==================================================

qla2xxx – 934.5.29.0-1vmw

qla4xxx – 634.5.26.0

qlcnic – 5.1.157

qlge – v2.00.00.57

In addition to that the drivers are also available in the VMware patch depot to be downloaded manually. These could be used to create a custom ESXi image using the “Image Builder CLI” or for a manual installation via CLI:

esxcli softwarev install -d

The offline bundles can be found in the download portal within the „Drivers & Tools” section, listed under “Driver CDs”. Those downloads also include the corresponding release notes.

This “mean” thing is that those drivers won’t be shipped via the Update Manager. Of course you could use the Update Manager to install them, but it will require to download them manually and to import them into the patch repository. Depending on the number of HBA/NICs this can be a bit cumbersome but it will be the only way to have them up to date other than updating the ESXi using a new image.

The KB article 2030818 (supported driver firmware versions for I/O devices) offers a link collection to the corresponding vendors like QLogic and their own VMware compatibility matrix. This matrix lists the latest driver version as well as the recommend firmware which should be applied accordingly.QLogicHCL

To check which version is currently installed on your host, you could also use the Update Manager or the following CLI command:

esxcli software vib listesxcli_software

To determine which driver is really actily used by the HBA can be verified via

esxcfg-scsidevs –aesxcli-scsidevs

But why is it actually important?

As with all pieces of software also drivers can contain bugs that need to be fixed or they get new feature, improved performance or support for new hardware devices. So if an outdated driver contains a bug which may affect the failover behavior of an ESXi host, this can have a significant impact on your environment!

By the way ESXi 5.5 introduced a new driver architecture called Native Device Driver. Currently a ESXi can run in hybrid mode to support the new and the “legacy” driver which is why the HCL currently shows two different types of drivers.


More useful links:

Identifying the firmware of a Qlogic or Emulex FC HBA (1002413)

Determining which storage or network driver is actively being used on ESXi host (1034674)

Installing async drivers on VMware ESXi 5.0, 5.1, and 5.5 (2005205)