none
SQL 2017 Cluster Availability Group Backup

    Question

  • Does DPM 2016 support backup of SQL 2017 Availability Groups?

    We upgraded to SQL 2017 this weekend and while the Cluster and Availability Group shows up in the DPM new/modify protection group wizard it won't populate with the database. Using the update data sources refresh button doesn't help. The SQL DB shows up in DPM under each of the individual servers in the cluster, it just won't show up under the availability group.

    Was working fine with SQL 2016. 

    Thanks.

    Monday, October 30, 2017 1:32 PM

All replies

  • Nobody can answer this?
    Tuesday, October 31, 2017 11:49 AM
  • i have the same problem. we are alone with this problem? 
    Wednesday, January 31, 2018 5:50 AM
  • Same problem here, just migrated, no backup option for AlwaysOn on SQL 2017. I bet the official statement will be that it is not yet supported.

    I can't understand that this can't be aligned, same company for backup and sql server so I would expect at least an update to the backup product to be released at the same time.

    Marc

    Thursday, February 1, 2018 2:12 PM
  • Anyone find a solution to this? Can't get anything in an AG protected now...
    Tuesday, April 3, 2018 10:16 AM
  • Hi,

    DPM does not support backing up SQL 2017 or SQL 2017 AG as of now and this is something soon will be added in the upcoming update.

    https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-1801

    ----------------------------------------------------------------------

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights.


    Thursday, April 19, 2018 11:31 AM
  • Hi Rahul,

    It seems that the matrix has been updated to include SQL 2017 support (dpm 1801 and 2016 ur5) but I still can't select alwayson databases to backup.

    https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-1801

    Is there any configuration required?

    Marc

    Friday, May 18, 2018 2:48 PM
  • Hi Rahul!

    I have the same problem. Yesterday we updated our DPM 2016 server to UR5 (5.0.361.0). Unfortunately SQL 2017 AG databases are still not expanded in the console:

    SQL 2017 AG

    SQL 2017 servers are fully patched (CU7). Is there anything else I can do?

    Kind regards,

    Anze


    Anze Stular

    Tuesday, June 5, 2018 6:39 AM
  • wait the  NEW UR ...    
    Friday, June 15, 2018 9:07 AM
  • Hi,

    DPM does not support backing up SQL 2017 or SQL 2017 AG as of now and this is something soon will be added in the upcoming update.

    https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-1801

    ----------------------------------------------------------------------

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting is provided "AS IS" with no warranties, and confers no rights.


    Hi Rahul - can you advise how long it will be until DPM 2016 Update Rollup 6 will be available? We can't go live with our SQL Server 2017 service until we have a working backup solution. Thank you!
    Wednesday, June 27, 2018 12:21 AM
  • Apologies for chiming in to an existing thread.

    I would also like to know If DPM 2016 can protect Databases in an SQL 2017 Availability group as I am just about to deploy a large number of SQL 2017 boxes and have opted for DPM 2016 as the backup solution.

    The Matrix https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-1801

    states the following for SQL 2017 - All deployment scenarios: database - surely this means Availability groups?

    If not, what is the answer - deploy SQL 2016? does DPM support protection of SQL 2016 availability groups?

    Thanks in advance for any advice.



    • Edited by MR_Rossi Wednesday, June 27, 2018 2:30 PM
    Wednesday, June 27, 2018 2:27 PM
  • Hi MR_Rossi,

    I deployed SQL 2017 AAG and I am unable to back them up with either DPM 2016 UR5 nor DPM 1801. I have a case open with MS to resolve this issue. According the support matrix both DPM 2016 UR5 and DPM 1801 state they support backup of SQL 2017 in all scenario's. All means all in MHO, so also AAG's

    I have also SQL 2016 AAG deployments which I can confirm these can be backed up with DPM 2016 and 1801.

    BR,

    Marc

    Friday, June 29, 2018 9:24 AM
  • Hi Marc,

    Thank you very much for the info, I guess I'll be deploying SQL 2016 and DPM 1801 then.

    I'll be keeping an eye on this forum to see if there are any devlopments with this issue.

    Thursday, July 12, 2018 9:52 AM
  • I have just updated to 1807 build of DPM (agent version 5.1.378.0). Protection agent is fine on the Windows 2016 server system hosting a SQL 2017 instance. DPM doesn't even see the SQL 2017 instance. It will show me all drives and shares of the to be protected SQL 2017 server. 

    Sassan Karai

    Friday, August 3, 2018 7:42 PM
  • May I know how you configure DPM for SQL Server 2016 Availability Groups? I've set secondary server as readable replica and set sysadmin role for \SYSTEM local account, but the availability groups can't be detected on DPM
    Sorry I ask another question in your thread
    • Edited by ktsrg Thursday, August 16, 2018 10:26 AM
    Thursday, August 16, 2018 10:23 AM
  • hi,

    CU5 of DPM 2016 ...

    not backup on alwayson sql 2017 ...

    any date ?

    Monday, September 17, 2018 12:26 PM
  • Hi,

    Same problem here. DPM 1807 and SQL 2017 AG. DPM cannot list the databases under the AG.

    It Would be good to know when will it be possible to protect those databases!!

    Thanks.

    Wednesday, September 19, 2018 1:51 PM
  • You guys get this resolved (1807 + SQL 2017 AOAG)?
    It's January now …..

    Thx - M.

    • Proposed as answer by ryaneynolds1 Thursday, February 14, 2019 11:55 AM
    • Unproposed as answer by ryaneynolds1 Thursday, February 14, 2019 11:55 AM
    • Proposed as answer by ryaneynolds1 Thursday, February 14, 2019 11:55 AM
    • Unproposed as answer by ryaneynolds1 Thursday, February 14, 2019 11:55 AM
    Monday, January 14, 2019 5:21 PM
  • Following a call with Microsoft, i can now backup a SQL Server 2017 Always on Cluster (one DB) with DPM 2016 UR5, DPM couldn't see the always on cluster. 

    Microsoft provided a replacement dpmra.exe which fixed the issue

    • Proposed as answer by ryaneynolds1 Thursday, February 14, 2019 11:58 AM
    Thursday, February 14, 2019 11:57 AM
  • Hi,

    Is this replacement dpmra.exe publicly available?

    Wednesday, February 27, 2019 11:40 AM
  • Hi,

     I was able to backup an SQL 2017 Cluster Availability Group database with DPM 2016 UR6. I just simple add  NTAuthority\System to the Sysadmin group on SQL Servers ( https://docs.microsoft.com/en-us/system-center/dpm/back-up-sql-server?view=sc-dpm-1807#prerequisites-and-limitations )



    Thursday, February 28, 2019 3:49 PM
  • Hi,

    Was there any fix from support? I am facing the same issue after upgrading DPM to version 2016-1807 the SQL-2017 Availability Group databases are not populating.

    Earlier with DPM-2016-UR6 the SQL 2017-DBs of Always-On were detecting and was able to backup

    My server is on platform Win 2016, the backup server on installed on SQL 2016 DB.

    Thanks & Regards

    Manu MS



    • Edited by Manu.MS Thursday, March 28, 2019 11:47 AM
    Thursday, March 28, 2019 11:46 AM