Exchange 2016 Healthy Copy - local to BE

Hi,

We have CASO:

Backup1 : actual backup server with dedupe storage
Backup2 : CASO
Mail1 : RAWS

Backup2 can browse Exchange databases on Mail1 just fine, but Backup1 also has Exchange installed and when I go to create a new job on Backup1 or Backup2 for any Exchange databases on Backup1, I get the message in the screenshot.

Exchange on Backup1 is brand new and all databases are mounted.

Tags (2)
3 Replies

Re: Exchange 2016 Healthy Copy - local to BE

No ideas?

Re: Exchange 2016 Healthy Copy - local to BE

What version of Exchange (including CU level) is installed on these servers?

And what version (20.?) of Backup Exec is currently installed?

Re: Exchange 2016 Healthy Copy - local to BE

From Exchange Management Shell:

Name : DUMMY01
Edition : Standard
AdminDisplayVersion : Version 15.1 (Build 1713.5)

Name : DUMMY02
Edition : Standard
AdminDisplayVersion : Version 15.1 (Build 1713.5)

That build number is CU12 (https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserv...)

From Help and Documentation > About Backup Exec:

Backup Exec 20.4 Rev. 1188 (64-bit)

So both Exchange Servers are as the same build number, only the one local to Backup Exec cannot be selected.