Veeam 7 Replication - source removed vmdk, target not update

[raymond.mui]

Hi, I understand that the version is very old. ~_~

Our source VM removed a VMDK. The replication job runs well. However, the replica still show the supposedly-deleted VMDK, but it was not replicated anymore. May I ask if Veeam should update the replica configuration to exclude the unnecesary VMDK?

Or, how can we update the replica config?

Thanks

Raymond

[veremin]

Chances are the said disk is still present in virtual machine configuration file, thus, it gets shown on a target host. Also, you can just exclude the supposedly-deleted VMDK from replica job processing to be 100% sure that it doesn't get replicated. Thanks!

[raymond.mui]

Thanks for your reply.

So, how does Veeam handle changes of VMDK in configuration file? I mean, would the changes in the source vmx file replica to the target's?

Thanks

[Vitaliy S.]

Yes, the VMX file should be updated with the new config. Is there any reason why you're still using this old version? What vSphere version are you at?

[raymond.mui]

VM is ESXi 5.0.0. As Veeam 7 is working well on it, we didn't upgrade it.

[raymond.mui]

In the source VMX, the VMDK is shown as

scsi0:2.present = "FALSE".

However, on the target (replica) VMX, the corresponding line shown:

scsi0:2.present = "true"

[foggy]

You can try to update the VMX file on target manually.

[raymond.mui]

Thanks foggy,

You mean edit the vmx to set the vmdk as present=false?

Really don’t want to start the replication from scratch as it is over 8TB for the eight vmdks

[Vitaliy S.]

You can make a copy of this VMX file and in case of any unexpected situations revert it back. Thanks!

[raymond.mui]

Thanks for the advices