Exchange 2016 with CU3

[scherrm]

Hi There

Our Exchange team is on the current CU3 of Exchange 2016, we have problems with the Netbackup since this status

Info bpresolver /pid=25468) done. status: 2
Error bpbrm (pid = 999) You can not use the BackupDirectory for Database Availability Groups for Exchange Standalone backup

We have a 6 Node Cluster wit a Exchange DAG
The Current Netbackup Client is 7.7.3

Thanks and Regards, Michael

[Marianne]

Is this a brand new config that has never worked before? 
Or did it work previously with a lower version of Exchange?

I see in the latest Agent CL that CU3 for Exchange 2016 is not yet supported. 
Only up to CU2. 

So, this is probably a compatibility issue for which there is no immediate fix.

[Michal_Mikulik1]

Hello,

according to DB compatibility list (https://www.veritas.com/support/en_US/article.000025229), Exchange 2016 CU3 is not yet certified with NetBackup.

Your Exchange team was to quick, they should discuss impact on all third-party products before any upgrades.

Ask your Veritas presale contact about timeline for CU3 support. Until them , you will probably have to use some MS native backup tool if any. Or at least keep one or more of your 6 DAG nodes as purely passive.

Regards

Michal

[scherrm]

Hi There,

On Exchange 2016 Cu2 ist works great, but after Update to CU3 it did not work anymore.

We open a ticket and hope for an earlier release

Regards
Michael

[Marianne]

Always good to check compatibilities before doing upgrades/updates.... 

[Lowell_Palecek]

It's been pointed out that Veritas has not yet announced support for CU3.

However, if you could post the bpresolver log with logging turned way up, we might see why bpresolver thinks your Exchange server is not part of a DAG.

Background:

The message, "You cannot use the backup directive for Database Availability Groups for an Exchange Standalone backup," is created by bpbrm when a backup file specification includes "Microsoft Exchange Database Availability Groups" and bpresolver reports that the client Exchange server is not part of a DAG.

The bprsolver status 2 is not a problem. That means it did not create a backup work list, which it was not asked to do. A subsequent bpresolver call would have done that if not for this error.