veeam backup job change protection group with powershell

[can]

Hello, I am trying to change the protection group via powershell after creating a backupjob in veeam, but there is no problem when I change it once, if I want to change it again after changing it, I get such an error, how can I solve this?

Code: Select all

$protection = Get-VBRProtectionGroup -Name test
$job2 = Get-VBRComputerBackupJob -Name "test2"
Set-VBRComputerBackupJob -Job $job2 -BackupObject $protection

Code: Select all

Set-VBRComputerBackupJob : The specified computer backup job is invalid.
Failed to validate a BackupObject with the specified name: test3. IndexIncludedOnly or IndexEverythingExceptExcluded options are not supported by Linux computer backup job of 
SelectedFiles type.
At line:5 char:1
+ Set-VBRComputerBackupJob -Job $job2 -BackupObject $protection
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-VBRComputerBackupJob], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Veeam.Backup.PowerShell.Cmdlets.SetVBRComputerBackupJob

[david.domask]

Hi can,

Which Veeam version are you using currently? I seem to remember there was an older issue with this cmdlet and it was resolved in one of the early v11 updates, so can you confirm if you're on v12 already? If not, please try upgrading and then see if the behavior continues. If it does, please open a Support case and let the Support Team review the issue.

[can]

hello I am actively using version 12.0.0.0.1420 p20230718, is there anything I can do for this version ?

[david.domask]

Hi can,

I would ask if you could please update to the latest version of Veeam Backup and Replication and see if the issue continues to reproduce; if it does, it's best to open a case and let the Veeam Support Team take a look at the behavior.

When you open a case, please share the case number here.

[oleg.feoktistov]

Hi @can,

What's your $job.IndexingOptions.IndexingMode value? Also, did you create your linux agent job via powershell?
Looks like I cannot reproduce the same issue in 12.0.0.1420, but you could try changing the existing indexing options.

Best regards,
Oleg

[can]

hello I realized that the structure I was trying to use was a different structure than the one that worked for me and I stopped researching this situation thank you for your help