none
Recovery point failed: RRS feed

  • Question

  • Hi,

    We have faced below issue while taking backup of SQL DB So Kindly suggest any solution to fix.

    ERROR:  

    Affected area: Database instance

    Occurred since:

    Description:        Recovery point creation jobs for SQL Server 2012 database   on Server have been failing. The number of failed recovery point creation jobs = 2.

     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)

                    Execution of SQL command failed for SQL Server 2012 database   on   with reason : BACKUP LOG is terminating abnormally.

    The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.

    . (ID 30173 Details: Internal error code: 0x80990D18)

                    More information

    Recommended action:  Check the Application Event Viewer logs on the SQL Server for entries posted by the SQL Server service to find out why the SQL command may have failed. For more details, look at the SQL Server error logs.

                    Create a recovery point...

    Monday, December 5, 2016 8:13 PM

Answers

  • Hi,

    does this Backup ever worked before`?


    Michael Seidl (MVP)

    SYSCTR Senior Consultant, Blogger, CEO

    Blog | Twitter | Facebook | LinkedIn | Xing | Youtube

    Note: Posts are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by Pmandyal Wednesday, December 7, 2016 5:16 PM
    Tuesday, December 6, 2016 10:00 AM

All replies

  • Hi,

    does this Backup ever worked before`?


    Michael Seidl (MVP)

    SYSCTR Senior Consultant, Blogger, CEO

    Blog | Twitter | Facebook | LinkedIn | Xing | Youtube

    Note: Posts are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    • Marked as answer by Pmandyal Wednesday, December 7, 2016 5:16 PM
    Tuesday, December 6, 2016 10:00 AM
  • Yes , it was worked 2 month before.
    • Edited by Pmandyal Tuesday, December 6, 2016 11:15 PM
    Tuesday, December 6, 2016 10:58 PM
  • Hi,

    Please help me on above issue.

    Monday, December 12, 2016 10:29 PM
  • Hi,

    please check the Database Recovery Model at the SQL Server.

    Like the error Message says, Log Type has been changed to simple, just make sure that it is.

    so we have 2 Options.

    Change back to Full

    or

    If you want to keep it simple, stop protection on the DB and re-add it to the protection group, SCDPM is then getting the new Recovery Modes from the SQL Server/DB


    Michael Seidl (MVP)

    SYSCTR Senior Consultant, Blogger, CEO

    Blog | Twitter | Facebook | LinkedIn | Xing | Youtube

    Note: Posts are provided "AS IS" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Tuesday, December 13, 2016 6:56 AM
  • Hi Michael,

    Thanks for your suggestion, but if I removed the protection group and re add then the restore point information which is earlier in the protection group has remove or not, I want to retain those restore point because we taking backup in the tape as well, If the information for RP is not there so we couldn't restore the backups from tape  

    Monday, December 19, 2016 7:02 PM
  • Hi,

    What Michael Seid has suggested is the correct course of action.  If you want the database to stay in simple recovery mode, then DPM needs to re-query the SQL server so it no longer schedules incremental backup jobs and just schedules express full jobs.   To do this, you need to stop protection and retain the replica and tape backups, then when you re-add the DB back to protection you need to REFRESH the protected server to update DPM cached information.

    See the following BLOG on the subject.


    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, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, December 19, 2016 7:20 PM
    Moderator
  • Hi Mike,

    I have perform the same as per your recommendation but after re add the protection group the issue is still

    there , Please provide any next course of action

    Wednesday, December 21, 2016 9:13 PM
  • Hi Michael,

    I performed as you suggest but the problem persist after performed the stop protection on affected DBs

    One more thing I added here

    In protection group multiple database instances has been backed up and only few are which failed due to simple recovery mode

    So need some clarification that I have to stop all databases or stop only effected  databases because I have stop protection for affected databases in the group so it is not fixed the issue.

    Please suggest

    Friday, December 23, 2016 3:07 PM
  • Hi ,

    Please assist on above issue.

    Wednesday, December 28, 2016 5:12 PM
  • Hi,

    You only need to stop protection and reprotect the one DB that is now in simple recovery mode. The refresh should have queried SQL Server to get it's recovery model.  Can you see what SQL reports for this SQL Query.  Put the name of the DB name in between the % signs in the below query and see what the recovery model is.

    use msdb
    SELECT server_name, database_name, backup_start_date, backup_Finish_date, recovery_model, is_snapshot, database_backup_lsn
    FROM backupset
    where database_name like '%DB_NAME%'
    order by backup_start_date desc


    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, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 9, 2017 5:09 PM
    Moderator