vSphere - turn off link the replica

[biotech]

Hello,

can somehow be turned off when you create a replication server to create a link in vSphere?

Thanks lot.

[veremin]

May I ask to elaborate a little bit on what you’re trying to do, since it’s not that clear from the provided information? Thanks.

[biotech]

I'm sorry,

We provide VM replication via Veeam backup.
After replication VM program will create a second VM on ESX server with prefix "_replica"

We would like to Veeam's VM does not create.

[veremin]

Actually, the suffix is always added in order to prevent having VMs with the same name in the infrastructure. However, you can leave the corresponding field ("Replica name suffix") blank , thus, no additional suffix/prefix will be created.

Thanks.

[dellock6]

Or, if you mean Veeam should create the replica on the target datastore BUT do not register it in the target ESXi (or cluster), I don't think is possible, even the replicated VMs are registered in the VMware infrastructure.

Luca.

[Vitaliy S.]

Actually you can skip this step (registration VM in the VI) by using vCenter Server granular permissions trick. Just do not specify "Virtual Machine - Inventory: Register" for the account used to connect to target vCenter Server and that's it.

[dellock6]

Nice one!
Thanks Vitaliy for the hint

Luca.

[biotech]

That's it.

Thank you

[veremin]

Should any additional help be needed, don’t hesitate to let us know. Thanks.

[meddie]

Hi,

i have a question because i didnt found some settings that could me help. I would like to let the Replicas on the target unregistered. So that them would be unvisible in the vCenter.
The reason is that a user has started a replica instead of the correct vm.

Can somebody helm me?
Thank you in advance
Greets Eddie

[Vitaliy S.]

Eduard, you can try a trick with a permissions list mentioned above to achieve your goal. Thanks!

[meddie]

Thanks, i will try it today. But i will get en error for this job because it cant complete it, or not?

[Vitaliy S.]

Yes, there will be a warning message saying that target replica cannot be registered in the VI.

[adrien.herve]

Hi guys,

Can you have a quick workaround to prevent a VM replica from being powered on on the target?

Thanks,

[foggy]

Adrien, do you mean to prevent others from powering the replica VM on manually?

[adrien.herve]

Yes. I have a DC replicated on my DRP site and I want to prevent this replicated VM from being powered on by my co-workers (it's on the same LAN so you guess why ).
On the target VM I try to disable my network adapter but of course it was overridden by the source at the next run of my replication job.

In the replication job we are able to change settings on the destination (host, ressource pool, VM folder and datastore) but I think it will be usefull if we can change guest settings for example to disable the network adapter on the destination VM.

My english is very poor today I don't know if it's clear, do you see what I mean?

[Gostev]

How about just using vSphere permissions?

[adrien.herve]

Yeah make sense, sometime I just need to have a different point of view.
That's a good idea I just need to change inherited administrator permission on these replicas to explicit permissions in read-only mode. Thank you Gostev!

[meddie]

Hi,

i have tried the trick to put the register Right off. But now the replica job gots an error and, everytime the job is running is veeam creating a new folder in the storage.
This Error:
Processing configuration Error: Die Berechtigung zur Durchführung dieses Vorgangs wurde verweigert.
Error: Die Berechtigung zur Durchführung dieses Vorgangs wurde verweigert.
(he permission to perform this operation was denied.)

I have an VM called TestReplikaVM
on the Replication Storage i have now

TestReplicaVM_replica
TestReplicaVM_replica_1
TestReplicaVM_replica_2
TestReplicaVM_replica_3

ans so on.

[Vitaliy S.]

Eduard, what version of vSphere are you using? When I was working on the granular permissions doc I didn't see that behavior in my lab.

[meddie]

Hi Vitaly,

we use vSphere 5.5.

I did this in this way:
i copied the role "administator" then in the new role i checked out the "register" right under virtual machine -> Inventary. Then i added my backup user to this new role which i called VeeamReplica. And at last i edited the permissions on the cluster and added my user with the new role.
When i edit this role and check in the right "register" the Replica Job works fine.

[Vitaliy S.]

Hmm... We will take a closer look at this scenario, it seems like the workaround mentioned above does not work anymore.

[meddie]

Thank you!