Guest Interaction Proxy mass change

[Manu80]

Hello,
we need mass disabling in many jobs the Guest Interaction Proxy from autodetect to specific proxy with Veeam Backup & Replication 12.0.
I search con documentation but I not find anything related to this.

I see this on the forum, post272191.html#p272191, but work fine ?

Thanks
Manu

[david.domask]

Hi @Manu80,

Yes, looks like unsupported methods are still needed for VM jobs (or I just can't find a supported method), though I can see we have supported cmdlets for at least Replica and Agent jobs, so hopefully we can see similar supported ways in a future release as the cmdlets continue to grow.

For now you can use the method from Tom in your link. A basic workflow for a single job that you can use in a loop over jobs would be:

Code: Select all

$GIP = Get-VBRServer -name 'ddom-veeam-rb4*'. #here you'd make your own capture for the desired Guest Interaction Proxy (GIP)
$job = Get-VBRjob -name 'vmware-ffi-cap-bb' #replace with your job name or just loop over jobs and write some code block to decide if changes are needed
$opts = Get-VBRJobVSSOptions -Job $job
$opts.GuestProxyAutoDetect = $false #Disable GIP auto-selection
Set-VBRJobVssOptions -Job $job -Options $opts #Confirm your changes in supported way

Job Name                  Type            State      Last Result  Description
--------                  ----            -----      -----------  -----------
vmware-ffi-cap-bb         VMware Backup   Stopped    Success      Created by DDOM-VEEAM-RB4\deeks at 8/29/2022 11:14...


[Veeam.Backup.Core.CJobProxy]::Create($job.id, $GIP.id, "EGuest") #this method is unsupported, but will create the necessary relationship -- this method takes 3 arguments in order as you can see, leave the last argument as the EGuest type as is shown


Id          : bfefa06e-eb5a-46f5-a435-1a3b3c5e87d3
ProxyId     : 6745a759-2205-4cd2-b172-8ec8f7e60ef8
Type        : EGuest
Info        : Veeam.Backup.Model.CJobProxyInfo
Job         : Veeam.Backup.Core.CBackupJob
ProxyServer : Veeam.Backup.Core.CWinServer

Note that the .NET reflection shown above is unsupported so if any issues, no support cases, but this is a pretty simple method and not a lot to mess up. Please be judicious in your code though as the unsupported method will let you add duplicate GIPs -- I think it's not such a big problem as at worst you'll probably get an ugly "sequence contains more than one element" or similar message on the jobs with duplicates, but I've not tested this and would advise just ensure via code you don't add duplicate GIPs

[OperaTTor]

hello , still unsupported method in 12.3 ? no powershell or rest api for this change? allso have more than xx job to edit each time manually via gui , will so easy to bulk this type of operation via api/posh. generally we disable automatic proxy in case of multiple Datacenter and to avoid cross I/O networking , and if we have a bunch of proxy in each dc , we want to reconfigure quickly in case of outrage of one dc.

[david.domask]

Hi Nicolas, welcome to the forums.

Still requires unsupported methods at this time. The method above should be safe, but regrettably it remains unsupported.

[OperaTTor]

it's can be a request Feature? ^^

[david.domask]

Sure, we can consider it a request, and there are already some plans on how to handle this moving forward, but nothing to share at this time. For now please use the above workaround.