none
SCDPM2012R2 - DPM was unable to determine the right node for backing up the Availability Group database and hence failed the backup. RRS feed

  • Question

  • I tried to protect the SQL 2012 AlwaysOn availability group but failed with the error message:

    DPM was unable to determine the right node for backing up the Availability Group database and hence failed the backup.
    Database: MSSQL-DAG\Temp-Database (ID 32029)

    I found similar error in another post but no one replied that thread.  Is it a bug in SCDPM2012R2?  I am so frustrated because last time I did lots of work to try to backup SharePoint 2013 with DPM2012 SP1/R2 but the final answer from Microsoft said that it's not supported if SQL Server 2012 AlwaysOn Availability Group was used.

    Backup is important, and it's a MUST in day one of the product launch.  I don't know why there isn't any solution from Microsoft. 

    Saturday, January 4, 2014 9:50 AM

All replies

  • Hi

    In SQL Always on configuration you can configure the backup to run a backup in the following way:

    Prefer Secondary – Automated backups for this availability group should occur on a secondary replica. If there is no secondary replica available, backups will be performed on the primary replica

    Secondary only – All automated backups for this availability group must occur on a secondary replica

    Primary – All automated backups for this availability group must occur on the current primary replica

    Any replica – Backups can occur on any replica in the availability group

    If for example the selected backup setting is Prefer Secondary. In order for DPM to find out which server holds a secondary role, it runs a SQL Query

    If the query can’t be ran at all, then we might see odd behaviors.

    Couple things that can cause this query not to run:

    1.        NT AUTHORITY\SYSTEM does have at least public permission on the SQL instance where the Always on is configured.
    2.        Can’t connect to SQL instance

    DPM is expecting one of these two responses: The always on group name or 0.

    If we can’t run the Query at all, we will get a null and null means the group isn’t ready for a backup and we will get the following event (DPM 2012 UI, Monitoring/Jobs tab

    Type:               Consistency check

    Status:             Failed

    Description:        DPM was unable to determine the right node for backing up the Availability Group database and hence failed the backup.

    Database:           <DB Name> (ID 32029)

    End time:           Date/Time

    Start time:         Date/Time

    Time elapsed:      

    Data transferred:  

    Cluster node        -

    Source details:    

    Protection group:  

    Items scanned:      0

    Items fixed:        0

    Recommended area to start troubleshooting the issue.

    From each SQL node during the Date/Time of backup failure review the DPMRA logs located in the following location <DPM Install Path>/Microsoft Data Protection Manager/DPM/Temp

    Identify if you have any Warnings being shown before the following is logged Normal AvailabilityGroup Role: NotReadyForBackup.

    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. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, January 9, 2014 1:50 PM
  • we are facing similar in one of our set up where we choose preferred secondary at SQLAG. could you let us know how to resolve it
    Saturday, September 29, 2018 12:21 AM
  • Hi Sivakumar,

    I suggest you create a new thread as this thread is already a few years old.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, September 29, 2018 3:12 AM