Get-VBRJobObject and "vm folders"

[theirpuppet]

Hello, I have a Backup Job that is configured with a single object: a vSphere 'VM Folder'. Unfortunately, Get-VBRJobObject only outputs that folder - not the VMs inside the folder.

Is there a Veeam provided CMDLET or mechanism to enumerate those VMs contained in that VM Folder?

Some interesting properties of the returned VBRJobObject (if they are relevant). Despite "isFolder = False", let me assure you that this is a VM Folder. It is not a Resource Pool or other object.

• $vbrjobobj.isFolder = False

• $vbrjobobj.Object.ViType = 'Folder'

• $vbrjobobj.Object.Type = 'Directory'

• $vbrjobobj.Object.Info.IsDirectory = True

• $vbrjobobj.Object.Info.IsFile = False

Thanks in advance!

[Egor Yakovlev]

Hi,
objects like VM Folders, Resource Pools, Datastores are dynamic - that is, Veeam does not know which VMs are currently in said folder\pool\datastore and we will query that information from vsphere each time job starts. So answer to your question is no, there is no Veeam Powershell cmdlet to query that information.
- you can query same info using vSphere PowerCLI cmdlet instead (Get-VM -Location $YourVMFolder)
- you can query Veeam job result(from sessions), and it will tell you which VMs were processed as a result of said job, however, note that it will not reflect current production state of said object, as it could change after backup job completion.
Hope that helps!

[theirpuppet]

Thanks, Egor. But I have found a solution:

$job = get-vbrjob -name "xxx"
$bkp = get-vbrbackup | Where-object {$_.jobid -eq $job.id}
$bkp.getobjects()

If I use the associated VBRBackup, I am able to retrieve the objects.
NB, the above is pseudo-code .. it may be syntactically incorrect.

[jhoughes]

There are some potential problems with that method, as a VM will only display after a backup job has run. It may also display VMs that were included in a backup previously, but may no longer be contained within a job.

Just be aware that it may not be 100% accurate, and it would only be accurate after the job runs if either job objects are changed, or if VMs are moved within the virtual environment.

[theirpuppet]

Thanks for the input, jhoughes.