Replicas with Active Full (corrupt chain)

[lang-ag]

We are having problems that some of our replicas (and normal backup ) VMs are corrupted.
We are not in trouble since this was just a test of our backup system.
That means that some (maybe 15 %) of the backed up VMs are either not booting up (windows recovery console window) or they are not working properly.
We tried going back to some earlier restore points and most of the problematic VM work without problems at the restore point before the last windows updates were automatically installed.

As a consequence all following reverse incrementals following from that date are also corrupt.
All the backup logs showed no problems.
We now changed the backup mode to incremental with weekly fulls to avoid similar problems in the future.

However I can't find an option to achieve the same with our replicas.
Some of them are also corrupt and I can't seem to find a way of doing a new full replica without deleting the jobs and replica Vms and recreating everything from scratch. (which would be a lot of work)
Any idea?

[foggy]

Christoph, there's the Active Full command available on the replication job's shortcut menu.

[VladV]

It is but it only works for backups.

I think the only possibility is to create another replica either by deleting it using the VBR console or, if you want to hold on to those restore points, you can remove it from VBR inventory without deleting it and then rename the replica from vSphere Client. Just be sure to write down which VMs are processed by which replication job because when you remove or delete the replica from the VBR console it will also remove the VMs from the replica job, thus you will need to re-add them.

[veremin]

You can revert replicas to the working snapshot (restore point), create a new replication job and map it to those reverted VMs. Once the jobs are finished, you will have two trustworthy restore points. Thanks.