Posting this to a new thread in case it gets buried in an old one
We did some initial setup checking that was covered in the following forum thread
The food chain we have in place is as followsMain Site
Data Host using VEB agent to backup a large data volume to a local VBR server/repository
BCJ on the local VBR server copying the VEB backup across WAN to a Veeam repository installed on a Windows server at the DR siteDR Site
Windows repository server with just the Veeam repository service running
Repository has result of the Main site BCJ - i.e. a backup chain from the VEB agent backup at the Main site
All good and as expected so far - and BCJ plays nicely over the WANHowever
If trying to do a VEB restore from a host at the DR site, the VEB (either file level or volume level) restore is looking for a VBR server it can connect to to tell it the location of repositories
It does not appear able to talk directly to a repository ?
But as this is the DR site, there is no connection to the Main site VBR (as would be the case in a disaster)
There is only the Veeam repository service running on the Windows repository server at the DR site
So does this mean that we would also have to have VBR running at the DR site
Just so that VEB can talk to VBR for it to tell it about a repository that it can then use ?
On the VEB agent have tried the following
If under OS I network mount the dir used by the repository and tell Veeam Endpoint Recovery that the backup is in 'local storage' it errors saying VEB cant open backups created by VBR
If in Veeam Endpoint Recovery I select instead 'network storage'
Then select 'shared folder' it ends up with the same error (not surprising)
If instead select 'Veeam backup repository'
It then asks for the IP for the Veeam backup server (as in 'specify VBR server to retrieve the list of backup repositories from')
The Windows repository server is only running the Veaeam repository service, so pointing to this end with error cannot connect with VBR server
Have we missed something?
Or does this mean that we also have to have VBR running at the DR site, so that VEB can talk to VBR for it to tell VEB about a repository ?
(and that would be VBR's only role at the DR site - i.e. to provision for a VEB recovery from a repository, VBR would be performing no backup functions)