Multiple B&R server, one for backup and one for replicas on 2 sites

[roland]

Hi guys
I wonder to know if this architecture will work and is supported by veeam v12.x
I use to build this in previous versions and it seems it's not working anymore now.

The objective of this architecture is :
Main Site : Backup all vms from vsphere to local repository with adapted retention and backup copy to some external ressource (vcc, cloud S3, etc ..) or tape backup
DR Site : Replica only criticals VMs to standby ESX.

In previous architecture i build a local Veeam B&R Server on main site with it's own repo and database. It's connected to main vcenter and backup all vms.
At the DR Site i build a second Veeam B&R only for replications of criticals VMs, connected to the main vcenter and to a standby standalone ESX.
In case of global outage on main site, i can restart quickly by performing failover on the DR site directly from the second veeam B&R server even if the main site is completely down.
I manage to avoid doing backup on server1 and replication on server2 at the same time, to be sure to have no locks.

For now the first full replica is working well, but any incremental fail with some kind of errors :
- Processing configuration Error: Unable to access file
- VM disk size changed since last sync, deleting all restore points
- Error: Unable to access file...
- Preparing replica VM Error: An error occurred while taking a snapshot: The parent virtual disk has been modified since the child was created
etc...

Something has change from v10 or v11 to V12 ? Is it supported or not in V12 ?
Any idea of architecture to do this now ?

Thanks for your help

[Andreas Neufert]

The setup should work as before.
I would check if I have the latest v12 version from the download section and update my v12 installation.
If this is not helpful, I think you should open a support case and upload logs there. Then please share support case number here fore reference. Thanks.

[roland]

My update test platform was done some weeks ago and is 12.1.2.172, i didn't see any concern in release note of 12.2