In 2016 I never thought that almost four years later I would still be working on my PowerShell script for a PRTG Veeam Sensor. But even shortly after the release of the two blog posts there was a surprise, Paessler, the Vendor behind PRTG, asked me if they could translate my article and publish it on their site. I was then as now surprised by this attention. And against all expectations, the PRTG Veeam Sensor has continued until today.
The first version of the PRTG Veeam Sensor (Translated version: Monitoring Veeam Backup & Replication using Veeam Enterprise Manager) was designed to use the RESTful API of Veeam Enterprise Manager to gather basic backup statistics. However, it quickly became apparent that this was not the optimal solution. Thanks to extensive feedback and the Veeam Reports from Shawn Masterson I was able the create the first version of the new PRTG Veeam Sensor. The new version was based on the PowerShell Snap-In for Veeam Backup & Replication. The Veeam Enterprise Manager was n longer required.
Basically, the PRTG concept for Advanced Sensors is quite ingenious. The EXE/Script Advanced sensor runs an executable file (.exe, .dll) or a script (batch file, VBScript, PowerShell) on the probe system. The return value of this sensor must be valid Extensible Markup Language (XML) or JavaScript Object Notation (JSON). In the case of the Veeam PRTG Sensor Reloaded PowerShell script, an XML is returned.
<prtg> <result> <channel>REPO - Default Backup Repository</channel> <value>64</value> <unit>Percent</unit> <showChart>1</showChart> <showTable>1</showTable> <LimitMinWarning>20</LimitMinWarning> <LimitMinError>10</LimitMinError> <LimitMode>1</LimitMode> </result> </prtg>
PRTG Veeam Sensor – Blog Statistics
Even in 2019 both Veeam PRTG blog posts still generated a lot of traffic on my small blog.
But even more amazing are the 290 comments on the Veeam PRTG Sensor Reloaded article. In my opinion that is a crazy number, even when 102 comments are created by myself as answers to questions.
PRTG Veeam Sensor – GitHub Statistics
Already in an early phase of the script, I had decided to start a GitHub Repository for the PRTG Advanced Sensors I have created by myself. This GitHub Repository has evolved into one of my most active projects over the years.
Issues: 7 Open / 26 Closed
Pull Requests: 0 Open / 16 Closed
Forks: 15
Stars: 28
Contributors: 4 (Thanks to Guy Zuercher, Eren Kemer, and Viktor Frelikh )
Contributions to the master branch, excluding merge commits:
PowerShell Script – What’s new
Over the last few years, the Veeam PRTG Sensor Reloaded script has evolved due to the many impulses and contributions from users of the sensor. This list highlights the major enhancement since the initial release.
Sep 11, 2017
The ability to monitor Scale-Out Backup Repositories was added and SAN Snapshot Repositories excluded.
Dec 3, 2017
Guy Zuercher added the ability to monitor Endpoint Backup Sessions and introduced the ability to select the monitoring scope (Backup, Replication, Agent, etc.).
Dec 17, 2018
Viktor Frelikh came to me with a great idea to adapt the Script for PowerShell Remoting. His modification males it possible to execute the script on the PRTG Probe but the Veeam PowerShell SnapIn is only required on the Veeam Backup & Replication Server. This solves two problems: No additional maintenance of the Veeam PowerShell SnapIn needs to be done after an upgrade and this a workaround for the problem that PRTG only uses PowerShell 32Bit which is not supported by the Veeam PowerShell SnapIn.
Dec 10, 2019
I have implemented a long-overdue improvement with the help of Chris Arceneaux. The script is now able to report Veeam Cloud repositories hosted by a Veeam Cloud Connect Service Provider.
PowerShell Script – What’s next
One major enhancement is 2020 might be the use of methods instead of Get-* Cmdlets. I already pushed a commit regarding this topic and then reverted it, because I am currently not able to test all cases that affect this change.
By the use of the methods, I expect an increase in performance but also a lot of testing needs to be done because the results of the method differ from the comparable Cmdlet.
Further, I expect some additional requests and required fixes as soon as Veaam Backup & Replication v10 GA is released:
- New Backup types like NAS Backup will certainly also be monitored.
- Endpoint Backup Cmdlets seems to be changed
Hi there
Thanks for maintaining and creating the script. However I have recently upgraded to Veeam BR 10 and I am trying to use your new script. version 1.8 however I am getting “The term ‘Disconnect-VBServer’ is not recognized as the name of the cmdlet.
Any advise?
Hi Ryan,
might you please open a new GitHub Issue for your Problem and add a few more details.
– PowerShell Version?
– OS Version?
– Veeam Version?
– Do you Execute via PSx64 or in PowerShell?
– Does the Veeam Console and the Veeam PS SnapIn work fine on you Box?
Best regards
Markus
Hi Markus,
I have the same problem as Ryan Brinch here. I am running Veeam Backup & Replication Version 10.0.0.4461 and I keep having that message :
The term ‘Disconnect-VBRServer’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
I am running PowerShell v5.1 both on my Veeam Server and PRTG Server and I am executing it from PSx64
I am running your script v1.8 and from the PRTG Program I have that error :
XML: The returned XML does not match the expected schema. (code: PE233) — JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)
So to have more details, I launch the PowerShell directly from my PRTG Server and it says :
The term ‘Disconnect-VBRServer’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name
I don’t really know where the problem can come from because it seems I can run Veeam PS Snapin without any problem on my Veeam Server (maybe because of the new snapin of the version 10?)
Hi Sebastien.
as you have also created a GitHub issue I will proceed there:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/62
Hi,
any chanche to get a Update for Veeam V11? they have changed from snapins to modules.
Cheers
Till
Hi Till,
I’m currently working on the v11 compatibility. I will update you as soon I have fixed all problems. The switch to modules is not the only change in v11.
Hi,
might please test this version of the Script:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/blob/vMarkusK-v11/Veeam/PRTG-VeeamBRStats.ps1
Hi Markus,
I testet it with the existing Sensor and with a newly created Sensor,
i can’t get it to work. I use the same User as before.
Logs:
Disconnect-VBRServer : Access to the path ‘Veeam\Backup’ is denied.
At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1:67 char:5
+ Disconnect-VBRServer -ErrorAction SilentlyContinue
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], UnauthorizedAccessException
+ FullyQualifiedErrorId : System.UnauthorizedAccessException
I can test further if you wish.
Hi,
Do you use PS remote?
Have you tried to execute the script on the vbr server itself?
Hi,
Thanks for your reply.
Yes I use PS remote because the remote Probe is on another server than the vbr server.
I tried now to execute the script on the vbs server itself. there it seems to work. Also on the remote probe server it seems to work in PS. But i cant get it to work in PRTG.
allways the error Message from above.
thanks for your time.
Thanks for the Feedback.
I have merged a change from an other github issue into the PR for v11 compatibility.
https://github.com/vMarkusK/Advanced-PRTG-Sensors/pull/76
Might you please verify that version as PS remote and an the vbr server itself?
Hi again,
sadly it wont work, always the same error:
Disconnect-VBRServer : Access to the path ‘Veeam\Backup’ is denied.
I testet the PS remote with the WSMan command and i looks well so far.
If i run the script in PS directly on the RemoteProbe or the VBR Servcer, i think the result is ok. its looks like this:
prtg>
Successful-Backups
1
1
1………………….
but in prtg it wont work. I always use the PSx64.exe to start the script with the parameters.
-f=”PRTG-VeeamBRStats.ps1″ -p=”srv-bkp01″
Kind regards
Till
Hi,
I don’t think you need PSx64 if you use PS remote. But anyway, it should not break the functionality.
Was your setup working before the v11 upgrade? I am asking because you do not use the PS remote switch.
A pretty robust solution is, installing a probe ob the vbr server and executing the script locally.
Best wishes
Markus
Hi,
yes everything worked finde before the Upgrade,
what do you mean with the PS remote switch?
I think i must use the PSx64 script to add the Script as sensor in prtg. or did I overlooked something?
for clarification:
we have a RemoteProbe Server with the VBR Console installed and updated to the same Version as the VBR Server.
I can connect without problems to the BAckup Server and I can run the Script localy on the VBR Server and on the Remote Probe Server. ( on remote Probe Server with the option -p=”srv-bkp01″) it looks good. but if I implement the script in prtg it shows only:
XML: The returned XML does not match the expected schema. (code: PE233) — JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)
and in the Sensor log it shows this:
Disconnect-VBRServer : Access to the path ‘Veeam\Backup’ is denied.
At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1:67 char:5
+ Disconnect-VBRServer -ErrorAction SilentlyContinue
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], UnauthorizedAccessException
+ FullyQualifiedErrorId : System.UnauthorizedAccessException
installing the remote probe on the VBR Server is not a option at the moment.
Kind regeards
Till
Hi,
You are right, your setup requires the PSx64 workaround. Because you do not use PS remote, it’s the normal remote connection of the veeaePowerShell module.
Have you tried to execute the script on the remote probe in a PowerShell x64 session (same user as prtg uses) ?
Might you please try to run the command including PSx64.exe in a PowerShell x86 prompt (same user as prtg uses) ?
I will create a lab with a similar setup to try to reproduce your problem.
Best wishes
Markus
hi, Markus,
Im sorry to take so much time from you. If you have a account where we can contribute you a few credits. just say.
probably i can not run the script directly in the x86 console.
but with the PSx64 i can run it, also with every user.
.\PSx64.exe -f=”PRTG-VeeamBRStats.ps1″ -p=”s19fri.xx.xxx.ch”
The result is everytime the same output no matter in which console or with which user.
here is a output with the debug option: (I removed the “” to display it right.)
PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML .\PRTG-VeeamBRStats.ps1 -BRHost s19fri.xxx -debug
DEBUG: Starting to Process Connection to ‘s19fri.xxx’ with user ‘svc_prtg’ …
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): A
DEBUG: BRHost ‘s19fri.xxx’ is Already Connected…
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): a
prtg
result
channelSuccessful-Backups/channel
value1/value
showChart1/showChart
showTable1/showTable
/result
result
channelWarning-Backups/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxWarning0/LimitMaxWarning
LimitMode1/LimitMode
/result
result
channelFailes-Backups/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelFailed-Backups/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelRunning-Backups/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
result
channelTotalBackupRead/channel
value64/value
unitCustom/unit
customUnitGB/customUnit
showChart1/showChart
showTable1/showTable
/result
result
channelTotalBackupTransfer/channel
value26/value
unitCustom/unit
customUnitGB/customUnit
showChart1/showChart
showTable1/showTable
/result
result
channelSuccessful-BackupCopys/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
result
channelWarning-BackupCopys/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxWarning0/LimitMaxWarning
LimitMode1/LimitMode
/result
result
channelFailes-BackupCopys/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelFailed-BackupCopys/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelRunning-BackupCopys/channel
value1/value
showChart1/showChart
showTable1/showTable
/result
result
channelIdle-BackupCopys/channel
value2/value
showChart1/showChart
showTable1/showTable
/result
result
channelSuccessful-Replications/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
result
channelWarning-Replications/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxWarning0/LimitMaxWarning
LimitMode1/LimitMode
/result
result
channelFailes-Replications/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelFailed-Replications/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelRunning-Replications/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
result
channelSuccessful-Endpoints/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
result
channelWarning-Endpoints/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxWarning0/LimitMaxWarning
LimitMode1/LimitMode
/result
result
channelFailes-Endpoints/channel
value0/value
showChart1/showChart
showTable1/showTable
LimitMaxError0/LimitMaxError
LimitMode1/LimitMode
/result
result
channelRunning-Endpoints/channel
value0/value
showChart1/showChart
showTable1/showTable
/result
DEBUG: Veeam.Backup.Model.CBackupRepositoryInfo
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): a
DEBUG: Veeam.Backup.Model.CBackupRepositoryInfo
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): a
DEBUG: Veeam.Backup.Model.CBackupRepositoryInfo
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is “Y”): a
result
channelREPO – s20fri Repository/channel
value14/value
unitPercent/unit
showChart1/showChart
showTable1/showTable
LimitMinWarning20/LimitMinWarning
LimitMinError10/LimitMinError
LimitMode1/LimitMode
/result
result
channelREPO – s21fri Repository/channel
value15/value
unitPercent/unit
showChart1/showChart
showTable1/showTable
LimitMinWarning20/LimitMinWarning
LimitMinError10/LimitMinError
LimitMode1/LimitMode
/result
result
channelREPO – s20fri BackupCopy Repository/channel
value14/value
unitPercent/unit
showChart1/showChart
showTable1/showTable
LimitMinWarning20/LimitMinWarning
LimitMinError10/LimitMinError
LimitMode1/LimitMode
/result
/prtg
Repository Name Free (GB) Total (GB) Free (%) Status
————— ——— ———- ——– ——
s20fri Repository 3555.23 26081.81 14 Warning
s21fri Repository 3848.31 26081.81 15 Warning
s20fri BackupCopy Repository 3555.23 26081.81 14 Warning
Successful Backups : 1
Warning Backups : 0
Failes Backups : 0
Failed Backups : 0
Running Backups : 0
Total Backup Transfer : 26
Total Backup Read : 64
Warning BackupCopys : 0
Failes BackupCopys : 0
Failed BackupCopys : 0
Running BackupCopys : 1
Idle BackupCopys : 2
Successful Replications : 0
Warning Replications : 0
Failes Replications : 0
Failed Replications : 0
Running Replications : 0
Seccessful Endpoints : 0
Warning Endpoints : 0
Failes Endpoints : 0
Running Endpoints : 0
Hi Till,
from my perspective, everything looks fine. For more robust results please use the -raw parameter for PSx64.exe
PS Native:
.\PRTG-VeeamBRStats.ps1 -BRHost WIN-RT26QHK0M11
PSx64:
.\PSx64.exe -f=”PRTG-VeeamBRStats.ps1″ -p=”WIN-RT26QHK0M11″ -raw
So, the script itself works fine. The problem seems to be related to PRTG, or how PRTG executes the Script.
The error in “VeeamBRStats.ps1:67 char:5” when you execute the script via PRTG does not make sense to me, there is no such command in this line. do you really use the latest version?
Latest Version:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/blob/master/Veeam/PRTG-VeeamBRStats.ps1
I assume that you hit the TRAP (which does a Disconnect). Try to remove Line 78 “Disconnect-VBRServer -ErrorAction SilentlyContinue” and check the logs after the next check.
I am very happy when you share my content with others. But also new GitHub sponsors are always welcome.
GitHub Sponsor: https://github.com/vMarkusK
PayPal Donation: https://www.paypal.me/mycloudrevolution
Best Wishes
Markus
Hi, I’ve been having issues running the script since i’ve updated to Veeam V11. I’ve downloaded the latest version from the github, and i’ve tried running it directly on our PRTG probe in Powershell, and that works fine. I also tried running it via CMD using the PSx64.exe command, and everything comes out fine.
However when I add the “EXE/script Advanced” sensor and point it to PSx64 with the same variable I use on the probe, it fails saying
“XML: The returned XML does not match the expected schema. (code: PE233) — JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)”
Any ideas on what could cause this?
Hi Johan,
do you have installed the VBR Console on the Probe or do you use PSremote?
Have you checked the logs of the PRTG sensor for more details?
Best wishes
Markus
Hi Markus
Yes i use the newest version, but i found out that the line differences commes from how you copied the script. If you copy the script directly from your link the ISE oder NotePad++ delets some empty lines. if you copy the script from the RAW view we get the same number of lines.
Now i use the script i copied from the RAW view. so the same error from above is on line 78 like you said.
If I delete the disconnect command on line 78 i get the following error in the sensor log from prtg:
#####################################################
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : Access to the path
‘Veeam\Backup’ is denied.
At line:1 char:1
+ &’C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : at ScriptBlock, C:\Program
Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1: line 308
at ScriptBlock, No file: line 1
At line:1 char:1
+ &’C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\P …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,PRTG-VeeamBRStats.ps1
prtg
error1/error
textAccess to the path ‘Veeam\Backup’ is denied./text
/prtg
#####################################################
on line 308 is the OpenConnection command.
I think i get no more relevant infos with the -raw parameter
best wishes and a nice weekend
Till
With the current findings and information, I can unfortunately only guess what the problem is.
As the script itself works and returns valid results the Problem must be related to the was PRTG initiates the command (permissions / context).
I have done another test with all the latest versions (PRTG, PSx64, and Script) without any issues.
Hi,
Yes, we have the latest VBR Console version installed on the Probe, so we use that instead of PSremote.
I’ve just activated storing of the sensor results, and the result file is completely empty. So it seems the output is simply null for some reason, which is really odd considering when i run it via the PSx64 via CMD directly on the probe, it returns the correct values.
Have you tried to start a CMD in “run As Mode” with the same security context the PRTG Probe uses for the Sensor?
Have you checked both log files (data.log and .log)?
Hi,
Yes, we’ve tried running it in “Run as mode” and i’ve also tried setting up a new “parent device” and setting the same securiry context as the account im using while testing on the server, but the same error persists. However today it actually logs an error, I get the following:
Get-PSSnapin : No Windows PowerShell snap-ins matching the pattern ‘VeeamPSSnapin’ were found. Check the pattern and th
en try the command again.
At C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\VeeamMonitor1.ps1:145 char:33
+ [int]$VbrVersion = (Get-PSSnapin VeeamPSSnapin).Version.T …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (VeeamPSSnapin:String) [Get-PSSnapin], PSArgumentException
+ FullyQualifiedErrorId : NoPSSnapInsFound,Microsoft.PowerShell.Commands.GetPSSnapinCommand
It’s odd that I can’t re-create this error on the server though, even when running the CMD with the security context of the probe and running the psx64 with the same parameters as in PRTG.
So the script itself seems fine, just for some reason I can’t figure out, it won’t load the Module correctly when run via the web gui
Hi Again,
It seems I’ve found the cause of the issue. For some reason PRTG won’t find the module when using: Import-module -name Veeam.Backup.Powershell as it claims it can’t find it.
However, if I after “-name”, specify the complete path to the Veeam.Backup.Powershell.dll, the script is successfull. So the script is working fine and as intended, and the issue seems to be on our server and it’s ability to load the Module at times.
I will investigate what is causing this, but for now i’ll simply work around the issue with the full path to the module DLL.
Thank you for all your responses and help Markus!
Hi Johan,
thanks for your feedback. I will also have a look into this.
I assume another user reported a similar issue: https://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/78
Hi Johan,
might you please test this version:
https://raw.githubusercontent.com/vMarkusK/Advanced-PRTG-Sensors/PSModulePath/Veeam/PRTG-VeeamBRStats.ps1
I have added a small hack to make sure PSModulePath includes Veeam Console.
Hi Markus
We are a step further now, but i think it is only a workaround.
If we placed the Computer Account from the remote probe in the local administrators group of the VBR Server. The Sensor works now with the “Use security context of PRTG probe service” setting. But not with the “Use Windows credentials of parent device” setting.
But as soon i remove the Computer Account the sensor fails. no matter if i choose “Use security context of PRTG probe service* or “Use Windows credentials of parent device” the Windows Account we use have locally Admin rights on the VBR Server. the both Servers are in the same domain so we can exlude this..
Now i testet it with the new Script but it’s the same error and behavior.
I have no idea why it wont work with the other setting. with V10 it worked like a charm with the same user.
best regards
Till
Hi Tim,
I am also confused as to why this setup worked with v10.
My recommendation was to start the probe service as an account with access to Veeam, or to start a probe on the VBR server itself.
“Use Windows credentials of parent device” does not work with Advanced Sensors (as far as I know).
See also:
https://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/77
https://github.com/vMarkusK/Advanced-PRTG-Sensors/issues/80
Hello, thanks for sharing your work, I have the same problem as with other scripts, they work for me on the Veeam server, but they don’t work for me on the PRTG server, the credentials are the same and I mark them “Use” Windows Credentials from primary device “, the following error message appears:
“Access was denied. To resolve this issue, please check your login details for Windows systems in device settings. (Code: PE095)”
The credentials are different on both servers
Thanks in advance
Versuche mal den Probe-Service als der User mit Veeam Berechtigungen zu starten, dass ist der zuverlässige Weg.