Making replicas simpler

[marius roma]

I have many replica jobs from a production site to a disaster recovery sites.
As VMs in the production site change during the time, replica jobs fail for various reasons, including:
- The source VM is modifyied (messages lik "Discovering replica VM Error: An error occurred while taking a snapshot: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child. - Error: An error occurred while taking a snapshot: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child.)
- The jobs makes replicas from a folder, and a VM in the folder was not jet replicated
- A replica VM got corrupted for any reason, including failed replicas
- ...
- ...
Is there any way to schedule replica jobs to replicate the source VM regardless possible problems at the target site, overriding target VMs if any problem occurs?
Regards
Marius

[foggy]

- The jobs makes replicas from a folder, and a VM in the folder was not jet replicated

In this case the job shouldn't fail but rather replicate the entire VM.

Is there any way to schedule replica jobs to replicate the source VM regardless possible problems at the target site, overriding target VMs if any problem occurs?

There're some mechanisms to force replication in case of source VM changes (VM hardware change, for example), however, not all the cases can be treated like that.