none
SQL incremental backup job is failing again and again -DPM 2019 RRS feed

  • Question

  • I am using DPM 2019 for SQL protection. But since the time, I created protection group, it is failing. Error is as below

    Error:

    Recovery point creation jobs for SQL Server 2012 database S300M\DBMaintenance on s300m.abc.com have been failing. The number of failed recovery point creation jobs = 5.
     If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)

    DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for  SQL Server 2012 database database S300M\DBMaintenance since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)

    Recommendation : 

    If you see this failure as part of a backup job, then in the Protection task area, select the SQL Server database and click Create recovery point. Choose express full backup. Alternately, you can wait for the next scheduled express full backup to run. 

    If this failure occurs as part of a recovery job, then try to recover from another point in time. 
    Review the Application Event Viewer logs on the computer running SQL Server for more details. 
    Ensure that this database is not already protected by another backup application.


    Arif

    Friday, October 9, 2020 9:23 AM

Answers

  • If something works it doesn't necessarily mean that it is supported, these are the official notes which can also be found in the official Microsoft documentation.

    Not supported often means that Microsoft has not tested this scenario, if you are running an unsupported scenario you may or may not receive support from Microsoft, that's why I recommend running a supported scenario.

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

    The reason incremental backups fail with the Error ID: 30140 - "Discontinuity in log chain" - Is that DPM maintains log chain sequence with every incremental backup.

    This sequence can be broken if user has scheduled native SQL Log backups or has log-shipping enabled (after protection with DPM).

    With these out-of-band log backups the log sequence maintained by DPM is broken and hence the failures seen.

    If you intend to have third-party log backups for databases and also use DPM, you can configure DPM to take only express full backups and no incremental backups (aka log backups).

    The way to do this is to choose the option 'Just before Recovery Point' for incremental backups during Protection group creation/modification.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by azahri miya Monday, October 12, 2020 4:45 AM
    Friday, October 9, 2020 10:21 AM
  • Thanks, I had checked with SQL owner, they had schedule some native backup method for T backup. After they disabled it, DPM started working good.

    Arif

    • Marked as answer by azahri miya Monday, October 12, 2020 4:45 AM
    Monday, October 12, 2020 4:45 AM

All replies

  • Hi Arif,

    DPM 2019 does not officially support protecting SQL Server 2012, refer to the supported SQL Servers over at the official documentation here:

    What can DPM back up?
    https://docs.microsoft.com/en-us/system-center/dpm/dpm-protection-matrix?view=sc-dpm-2019

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, October 9, 2020 9:56 AM
  • But it is supporting backup, my rest other backups are working fine. Even I had logged case with MS, they helped me to configure backup for SQL 2012 and it is running without issue. If I create manual recovery point whether full or incremental, it runs successful. Some old job were successful, i performed a test restore and shown to app owner, it worked. So I think, DPM is still supporting SQL 2012


    Arif

    Friday, October 9, 2020 10:14 AM
  • If something works it doesn't necessarily mean that it is supported, these are the official notes which can also be found in the official Microsoft documentation.

    Not supported often means that Microsoft has not tested this scenario, if you are running an unsupported scenario you may or may not receive support from Microsoft, that's why I recommend running a supported scenario.

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

    The reason incremental backups fail with the Error ID: 30140 - "Discontinuity in log chain" - Is that DPM maintains log chain sequence with every incremental backup.

    This sequence can be broken if user has scheduled native SQL Log backups or has log-shipping enabled (after protection with DPM).

    With these out-of-band log backups the log sequence maintained by DPM is broken and hence the failures seen.

    If you intend to have third-party log backups for databases and also use DPM, you can configure DPM to take only express full backups and no incremental backups (aka log backups).

    The way to do this is to choose the option 'Just before Recovery Point' for incremental backups during Protection group creation/modification.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by azahri miya Monday, October 12, 2020 4:45 AM
    Friday, October 9, 2020 10:21 AM
  • Thanks, I had checked with SQL owner, they had schedule some native backup method for T backup. After they disabled it, DPM started working good.

    Arif

    • Marked as answer by azahri miya Monday, October 12, 2020 4:45 AM
    Monday, October 12, 2020 4:45 AM