Sorry about that.
Restore Points at Replicas are held in VM Snapshots and the Target VM is only started at a failover. Therefore you can not use VMware change block trackig (CBT). Without this you would have to read 100% of the data each backup run to find the changes. This is not good and we do not support this for that reason and some others.
What you can do is the following.
On Primary side create a backup job to a local backup target (repository). Then create a Backup Copy Job (BCJ) to the second site. This BCJ will store the backup data again in a Repository. When you create a Replicat Job, you can select the Source of the Replica (Source button). There you are able to select the BCJ Repository as Source instead of the original VM. Data Flow is: Original VM => Backup Job => Repository Site 1 => BCJ => Repository Site 2 => Replica Job => Replica VM
If you use Veeam WAN Accelerators for the Replica Job, you can use them with the BCJ as well.