Forum Discussion

mhale's avatar
mhale
Level 2
4 years ago

SharePoint credential failure with SQL Availability Group

We are trying to use Backup Exec 21.1 to protect a SharePoint 2016 farm that is sitting on top of a SQL 2016 Availability Group.  I understand the capability to back up availability groups is new in ...
21
Availability Group
sharepoint
SQL
Windows Server 2016
  • P_Jeal's avatar
    P_Jeal
    4 years ago

    I am sorry to advise that while SQL Availability Group support was added in Backup Exec 21.1, that is for SQL Agent backups only. Sharepoint Agent backups do not yet support SQL Availability Groups.

    This mentioned as a note in the start of the 'Agent for Applications and Databases Compatibility' section of the Software Compatibility List (https://www.veritas.com/content/support/en_US/doc/BE_21_SCL)

    • Backup Exec does not support protecting SharePoint Server which has its Databases configured on SQL Always On Availability Groups.

    I understand this can easily be overlooked, if reviewing only the relevant product tables below that.

P_Jeal's avatar
P_Jeal
Moderator

I am sorry to advise that while SQL Availability Group support was added in Backup Exec 21.1, that is for SQL Agent backups only. Sharepoint Agent backups do not yet support SQL Availability Groups.

This mentioned as a note in the start of the 'Agent for Applications and Databases Compatibility' section of the Software Compatibility List (https://www.veritas.com/content/support/en_US/doc/BE_21_SCL)

• Backup Exec does not support protecting SharePoint Server which has its Databases configured on SQL Always On Availability Groups.

I understand this can easily be overlooked, if reviewing only the relevant product tables below that.

mhale's avatar
mhale
Level 2
4 years ago

Oh.

Well that isn't the answer we were looking for but I appreciate it nonetheless.

I know better than to ask when we might expect support :) however I can't believe we are the only BE users to be running SharePoint in this way.  It is one of Microsoft's recommended configurations, after all.  What I will say is I hope support comes soon before we are forced to consider other solutions.

Thanks.