Markus Kraus

Is the PRTG Core server the only Probe in your environment? Service is restarted after the change? I am not sure what's the reason for this message (maybe the local...

Sorry, bus this sounds definitely like a permission issue. > An other workaround is installing a probe service on the veeam Server itself and move the sensor to this probe....

Please have a look at this new and enhanced Version: https://github.com/vMarkusK/Advanced-PRTG-Sensors/blob/master/Veeam/PRTG-VeeamBRStats-v3.ps1

@IcyPunch have you upgraded to vbr console on the probe? Please have a look at the v2 version of the script in the repo. This might solve a lot of...

> @vMarkusK > > I have used this one today, is it incorrect?: > >  That's the right one. With that version you do not need the PSX64.exe anymore....

Hi, the "Get-vPCRepoInfo" function precesses all Datastores in your Veeam Inventory. Had something changed in your Veeam Environment (new or changed Repo, etc.)? Do you use the latest version of...

Hi @cerri , Do you use the -selChann parameter to change scope of the script? Which VBR version do you use? Might you please run the script run with -Debug...

I created a playbook that temporarily migrates the VM to a standard PG, does the vMotion and cleans up the workaround afterwards.

No, it's another cluster, dvs and Datacenter

Right. Temporarily PG only on the source an destination host and a cleanup afterwards.