You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the install I get this error when backup jobs on the B&R are Computer Agent Backups.
Job Configuration Selection
Do you wish to configure all supported jobs, make a decision for each job, or configure none?
[A] All [D] Decide [N] None [?] Help (default is "A"): a
: This cmdlet is not supported for computer backup jobs. Use Set-VBRComputerBackupJob instead.ion.ps1: line 269
When I change the line 269 in the 'resources\DeployVeeamConfiguration.ps1' file to Set-VBRJobOptions -Job $job -Options $jobOptions | Out-Null the following output is displayed:
Job Configuration Selection
Do you wish to configure all supported jobs, make a decision for each job, or configure none?
[A] All [D] Decide [N] None [?] Help (default is "A"): a
: A parameter cannot be found that matches parameter name 'Options'.rces\DeployVeeamConfiguration.ps1: line 269
So... I removed the options switch on line 269 so it looks like this: Set-VBRJobOptions -Job $job | Out-Null
Then it succeeded.
Steps To Reproduce
No response
VeeamNotify version
v1.0
PowerShell version
5.1
Veeam Backup & Replication build number
12.1.0.2131
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
When running the install I get this error when backup jobs on the B&R are Computer Agent Backups.
When I change the line 269 in the 'resources\DeployVeeamConfiguration.ps1' file to
Set-VBRJobOptions -Job $job -Options $jobOptions | Out-Null
the following output is displayed:So... I removed the options switch on line 269 so it looks like this:
Set-VBRJobOptions -Job $job | Out-Null
Then it succeeded.
Steps To Reproduce
No response
VeeamNotify version
v1.0
PowerShell version
5.1
Veeam Backup & Replication build number
12.1.0.2131
Relevant log output
No response
The text was updated successfully, but these errors were encountered: