Commvault VSA job fails with “The option to backup only failed virtual machines was selected, but no failed virtual machines were discovered in the previous job”

Commvault introduced a neat little option called “Backup Failed VMs only (Virtual Server)” which can be found in the advanced settings of the schedule policy backup task.

I reconfigured the schedule policy according to the following strategy:
(i) Backup task 1: daily incremental @ 7PM CET
(ii) Backup task 2: weekly synthetic full @ 10AM CET (DASH full only; no backup)
(iii) Backup task 3: daily incremental for failed virtual machines only @ 6AM CET

Continue reading

Link raw device mappings to the LUNs on the storage array

When a LUN is presented to a physical Windows server it’s more easy to link the LUN to the mounted disk within the operation system.
You can simply open the Disk Management tool (diskmgmt.msc) and click on the properties of the disk itself (not the partition!).
On the general tab, you can find the LUN number in the Location section.

In our case some LUNs are directly presented to a virtual machine running Windows 2008R2 (Raw Device Mappings). The disks itself are used within a virtual cluster configuration.
The customer asked me to identify the disk within the virtual machine together with the disk on the storage array (HP EVA 8400).
If you think this should be an easy task, think twice! The procedure below will be able to assist you in this matter.
Continue reading

Recover master password VMware vSphere 5.1 Single SignOn

Update: VMware provides a procedure in unlocking and resetting the account. This procedure can be found here:

I recently was at a customer for a Symantec Backup Exec installation. The customer Active Directory domain was configured as 2 child domains and one parent domain. The parent domain is used in their main site(s), the child domains are used for the remote branches (EMEA / US). On each location a VMware environment is installed with a dedicated Virtual Center server. As authentications are required for users within each domain, several LDAP strings are defined in SSO (https://vcenter:9443).

These LDAP queries are pointed to a set of servers (the Domain Controllers). When a domain controller is demoted or deleted, the LDAP queries are non-functional… And that’s what happened here! So the LDAP configuration needed to be altered. Quickly I discovered this is only possible by using a local SSO account! The default SSO account (admin@System-Domain) has some kind of master password that needs to be entered when reconfiguring the software component. It’s extremely important this password is written down and stored in a safe location as alternation of the password is impossible (cfr. VMware support).

Continue reading

List the multipath policy per datastore

Some jobs require several mouse-clicks to get the information you need. If this is for a limited amount of checks, doing it this way is more than acceptable. However in my situation I needed to check a vSphere 5.0 vcenter with 9 clusters, 49 hosts and 931 virtual machines. My task was to document each datastore together with the defined MultipathPolicy. I thought it would be a simple task with a PowerShell command that looks like this: get-datastore | select name,multipathpolicy or get-scsilun -luntype disk | select name,multipathpolicy.

In fact the solution is more complex than expected. If you want the human readable names of the datastores, you need to filter out the name by using the ExtensionData.

FOREACH($vmHost in (Get-VMHost))
Write-Warning "Grabbing Data for $vmhost"
FOReach($lun in ($vmHost|Get-ScsiLun -luntype Disk))
$collect=""| select "Host","Datastore","Canonicalname", "MultipathPolicy"
$Datastore=(Get-Datastore|?{($|select -expand diskname) -like $canon}).name
$output | Out-File C:\datastoresprod.csv

Credit goes to the persons who deserve it.

PowerCLI – list virtual machines with physical SCSI controllers & inventory path within vcenter

For a project, we needed to implement a VEEAM Backup & Replication setup. During the project we encountered some virtual machines with Physical RDMs. VEEAM cannot handle this, so it was needed to write a script allowing us to list all virtual machines with their most interesting parameters, such as:

  • Virtual Machine Name
  • Version
  • PowerState
  • HardDisks
  • ProvisionedSpaceGB
  • Datacenter
  • Cluster
  • InventoryPath
  • HasPhysicalController

The function Get-VMFolderPath can be found on this blog.

Continue reading