We're replicating our backups between two sites using the storage backend (FreeNAS arrays) - it's a lot faster than the Veeam replication and removes load from the VBR server. One of the quirks of this approach is that the destination for the replicas is read-only - see here for details on that - but one can easily make the replica r/w for the purposes of mounting the location as a backup repo. It will automatically set itself back to r/o when the next snapshot replica is sent.
I know Veeam can pull down immutable B2 replicas for restore, but when I try to use the NFS repo pulling from a read-only filesystem I get:
foggy wrote:
Entire VM restore doesn't need write access to the repository - I'd ask our engineers to review the log files for exact reason of the failure.
I will do that. It looks like the issue occurs when I go to refresh the repo.
'If you truly love Veeam, then you should not let us do this ' --Gostev, in a particularly Blazing Saddles moment