Add-VBRViReplicaJob limited?

[stephaneb]

Hi,
It seems impossible to specify a cluster as the destination using Add-VBRViReplicaJob when you can do it in the GUI.
Am I missing something?

Is it also possible to specify datastore clusters as a destination for a replica job?

Thanks.

Stephane

[veremin]

Hi, Stephane, it seems impossible, indeed, to specify cluster as a target for replication job through Veeam PowerShell Snap-in. Thanks.

[Andreas Neufert]

Solution is to set a ESXi host first and later change the option to a cluster.

[pllove]

The mentioned solution to set it back to the cluster setting, was this from PowerShell or the GUI? I have not been able to get the powershell command to work. Set-VBRViReplicaJob -job JobName -server ClusterName

Only thing I can get to work is if I use the hostname for the -server.

[veremin]

Andreas seems to have been talking about changing this setting via GUI, indeed. Thanks!

[Andreas Neufert]

OK some years passed, but I think you can set it first by PS to Host and in the next run change it to cluster?

[tsightler]

It's been quite a few years, but I believe even after all these years the method still works to create the job with a server, then change it to cluster. The general idea is in the script on this post:

powershell-f26/add-vbrvireplicajob-comm ... tml#p75237

But might need to be modified slightly for recent 9.5 updates to use the Get-VBRJobOptions/Set-VBRJobsOptions cmdlets.

[pllove]

Yes, between this thread and another where I found a pdf link to a veeamon pdf from 2018 I found that I had to use the Job options to set it back to a cluster setting instead of a host. I tried to do this in a script where I was modifying other settings (Destination settings and network mappings). I made my other settings and then tried issue the command to set the destination back to the host. What I found was that because I was doing that several settings were reset and the network mappings were completely wiped out. The answer was to use the Get-VBRJob command again to pull in the job settings and reset my variable I was using. This had to be done right before I used the job options to reset it back to the cluster setting.

[veremin]

Can you post the resulting script here, may be there is a room for potential improvement? Thanks!