The behavior is expected. Once you've added the host in v9 console, the Veeam B&R components installed on it were upgraded to the new version, which v8 console cannot communicate with. Adding the same servers into two Veeam B&R consoles of different versions is not supported.
foggy wrote:The behavior is expected. Once you've added the host in v9 console, the Veeam B&R components installed on it were upgraded to the new version, which v8 console cannot communicate with. Adding the same servers into two Veeam B&R consoles of different versions is not supported.
It would be nice if this was possible for a large environment to transition from v8 to v9 on multiple servers instead of having to upgrade everything at once.
You can install separate VB&R v9 server and start to add hosts to it one by one, waiting some time before adding a new one, to make transition from v8 to v9 more smooth. Thanks.
Hi,
Proxy and backup server only communicate if they run same version (we cannot mix versions), but can a CIFS repository be shared between a v8 and a v9 veeam infrastructure ?
What about a Windows repository ?
CIFS repositories can be shared between different versions of the software so long as they use different gateway servers. Communication between a gateway and a NAS is just SMB protocol, it inherently has nothing to do with your version of Veeam.
Windows repositories cannot be shared between versions.
I've seen Linux repositories shared between versions in the past, but I haven't verified that recently.
jp34 wrote:Hi,
Proxy and backup server only communicate if they run same version (we cannot mix versions), but can a CIFS repository be shared between a v8 and a v9 veeam infrastructure ?
What about a Windows repository ?
The CIFS repository can be set both v8 and v9. The only thing that can not be is the server itself hyperv