Hello,
I ran into a strange issue with the Veeam Find-VBRViEntity Cmdlet when PowerCLI Modules are loaded:
PS C:\Users\Administrator> Find-VBRViEntity
WARNING: One or more errors occurred.
Id Name Path
-- ---- ----
49500DBE-39E7-4A3E-A48B-3F995D1EFF63 Hosts and Clusters
e5f8ee73-cd14-4333-bf38-b7b14b2392f0 192.168.3.101 192.168.3.101
PS C:\Users\Administrator> Find-VBRViEntity
WARNING: Object reference not set to an instance of an object.
Id Name Path
-- ---- ----
49500DBE-39E7-4A3E-A48B-3F995D1EFF63 Hosts and Clusters
e5f8ee73-cd14-4333-bf38-b7b14b2392f0 192.168.3.101 192.168.3.101
The expected output of the Cmdlet is:
PS C:\Users\Administrator> Find-VBRViEntity
Id Name Path
-- ---- ----
49500DBE-39E7-4A3E-A48B-3F995D1EFF63 Hosts and Clusters
e5f8ee73-cd14-4333-bf38-b7b14b2392f0 192.168.3.101 192.168.3.101
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_datacenter-2 Lab 192.168.3.101\Lab
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_domain-c225 Cluster01 192.168.3.101\Lab\Cluster01
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_host-9 esxi-01.lab.local 192.168.3.101\Lab\Cluster01\esxi-01.lab.local
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-189 test19 192.168.3.101\Lab\Cluster01\test19
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-184 test14 192.168.3.101\Lab\Cluster01\test14
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-179 test9 192.168.3.101\Lab\Cluster01\test9
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-14 PhotonOS 192.168.3.101\Lab\Cluster01\PhotonOS
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-180 test10 192.168.3.101\Lab\Cluster01\test10
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-185 test15 192.168.3.101\Lab\Cluster01\test15
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-186 test16 192.168.3.101\Lab\Cluster01\test16
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-182 test12 192.168.3.101\Lab\Cluster01\test12
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-175 test5 192.168.3.101\Lab\Cluster01\test5
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-190 test20 192.168.3.101\Lab\Cluster01\test20
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-188 test18 192.168.3.101\Lab\Cluster01\test18
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-18 test2 192.168.3.101\Lab\Cluster01\test2
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-17 test3 192.168.3.101\Lab\Cluster01\test3
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-183 test13 192.168.3.101\Lab\Cluster01\test13
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-177 test7 192.168.3.101\Lab\Cluster01\test7
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-15 Veeam-03 192.168.3.101\Lab\Cluster01\Veeam-03
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-174 test4 192.168.3.101\Lab\Cluster01\test4
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-176 test6 192.168.3.101\Lab\Cluster01\test6
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-16 test 192.168.3.101\Lab\Cluster01\test
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-187 test17 192.168.3.101\Lab\Cluster01\test17
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-181 test11 192.168.3.101\Lab\Cluster01\test11
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_vm-178 test8 192.168.3.101\Lab\Cluster01\test8
e5f8ee73-cd14-4333-bf38-b7b14b2392f0_host-228 esxi-02.lab.local 192.168.3.101\Lab\Cluster01\esxi-02.lab.local
The expected output is generated in the same system. But the difference is:
- Load Veeam Snapin / Connect VBR Server -> Cmdlet works fine
- Load Veeam Snapin / Connect VBR Server / Load VMware Modules / Connect vCenter Server-> Cmdlet does not work
- Load Veeam Snapin / Connect VBR Server / run Find-VBRViEntity / Load VMware Modules / Connect vCenter Server-> Cmdlet works fine
My used Versions:
- PowerShell 5.1
- Veeam 9.5 U3a
- VMware PowerCLI 11.0.0
- VMware vCenter 6.5 U2
Might someone please try to reproduce my findings?
Has someone hit a similar problem?
Best regards,
Markus
https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
