Git Product home page Git Product logo

prtgsensors's People

Contributors

lordmilko avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

Forkers

opoet7 yarikosss

prtgsensors's Issues

Error while running Veeam Script

When I run the Get-VeeamBackupStatus script I get the following error. The parameters seem to be correct.

<Prtg>
1
An exception occurred while trying to process backups: Execution environment cannot be initialized to Remote

Anyone have an idea?

Get-VeeamBackupStatus in Error

Script return error if the field "NextRun" of a backup job is setting "After JobName"

1 An exception occurred while trying to process backups: String was not recognized as a valid DateTime.

image

Andrea

An exception occurred while trying to process backups: Access to the path 'Veeam\Backup' is denied.

Hi,

I read the guide, installed the B&R console and put the Get-VeeamBackupStatus.ps1 script and corresponding lookup into place. A Windows user who has the Veeam Backup Administrator role is saved in the device which I added the sensor to and the sensor is set to "use Windows credentials of upstream device".
Now when the sensor does a query, I get the following result:

DEBUG: Entered Main
DEBUG: Entered [VeeamBackupStatus]::GetStatus
DEBUG: Entered [VeeamBackupStatus]::GetStatusInternal
DEBUG: -Loading Veeam PSSnapIn
DEBUG: -Connecting to Veeam Backup Server
<Prtg>
    <Error>1</Error>
    <Text>An exception occurred while trying to process backups: Access to the path 'Veeam\Backup' is denied.</Text>
</Prtg>

If I run a powershell on the probe system as the above-mentioned user, and execute the script with the same parameters as entered in the PRTG sensor, it returns the backup data as intended. Also, in the same PS session, Connect-VBRServer works fine.

The path in the error message ('Veeam\Backup') looks like a substring of the path to the Veeam PS SnapIn ("C:\Program Files*Veeam\Backup* and Replication\Console\Veeam.Backup.PowerShell\Veeam.Backup.PowerShell.psd1"), although, according to the DEBUG entry above, the SnapIn was already loaded when the error is returned.

I am at a loss here. Any suggestions? Thanks in advance.

thwgha

An exception occurred while trying to process backups: Die Zeichenfolge wurde nicht als gültiges DateTime erkannt.

We also use schedules that run after other backups (parent jobs). These lead to this error.
As a work a round I have included the following in the script to intercept the call:
if ($this.job.ParentScheduleId -eq $null -or $this.job.ParentScheduleId -eq ""){
...[TimeFormatter]::GetNextBackupStartTimeText($epSchedule.NextRun)
}

It would be nicer if the schedule could be read from the parent job.

Backup Copy Job error "Could not find a handler for job type ''

I'm using this script to check the status for 2 Backup Jobs and 1 Backup Copy Job running on Veeam 12
Both the Probe and the Backup Server are 2019 in the same domain.

I have no Problem with the backup Jobs and I'm getting the corrct results in PRTG
Howerver I can't figure out the Problem with the Backup Copy Job and keep getting the error "Could not find a handler for job type"

1st I thought the Problem is because the Backup Copy Job is set to run after one of the backup Jobs (as new restore Point appears) so I changed the setting and set it to run separately on a different day, but that didn't solve the problem.
Any Idea how to solve this?

Paremetres, not reading Job Name

Hi there!

I am new using PRTG and this is the first custom sensor I've added.
No matter if I type double quotation marks or single ones when I set up the sensor, I always get the error:

"Please specify the name of a backup job. If the job name contains spaces, surround the name in double quotation marks."

It gets well the name of the server and credentials though.

How could I check what's wrong or any other idea?

Thanks in advance,

A.

Veeam sensor error: An exception occurred while trying to process backups: The term 'TapeJob::GetAll' 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.

Hi,

I'm getting an error while reading Windows Agent Backup in Veeam. The following error im getting: An exception occurred while trying to process backups: The term 'TapeJob::GetAll' 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.

It's a separate backup job based on Windows Agent Backup

Any suggestions?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.