none
log shipping Could not retrieve backup settings for primary ID

    Question

  • hello,

    I implemented log shipping in our server the process of implementation went fine but when I view job history I found

    Message
    2014-06-11 12:00:01.53    *** Error: Could not retrieve backup settings for primary ID '99817903-626e-4380-bcf1-c09ca6f48b6d'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
    2014-06-11 12:00:01.53    *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
    2014-06-11 12:00:01.53    *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-06-11 12:00:01.53    *** Error: The specified agent_id 99817903-626E-4380-BCF1-C09CA6F48B6D or agent_type 0 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
    2014-06-11 12:00:01.53    ----- END OF TRANSACTION LOG BACKUP   -----

    Exit Status: 1 (Error)

    also I check for database ID using select * from msdb..log_shipping_primary_databases

    your help is appreciated.


    Please Mark it as Answered if it answered your question
    OR mark it as Helpful if it help you to solve your problem
    Elmozamil Elamir Hamid

    MCSE Data Platform
    MCITP: SQL Server 2008 Administration/Development
    MCSA SQL Server 2012
    MCTS: SQL Server Administration/Development

    MyBlog

    Wednesday, June 11, 2014 9:20 AM

Answers

  • Thank you all for your contribution.

    After testing and debugging I found that when they move their database from one server (server2) to another server (server1) the database still using the old name (server2) which you can findusing this script:

    SELECT @@SERVERNAME

    so the replication can't retrieve information, unfortunately for me it is difficult to rename the server because it sis development server so they need to make analysis about side effects if we renamed it. 


    Please Mark it as Answered if it answered your question
    OR mark it as Helpful if it help you to solve your problem
    Elmozamil Elamir Hamid

    MCSE Data Platform
    MCITP: SQL Server 2008 Administration/Development
    MCSA SQL Server 2012
    MCTS: SQL Server Administration/Development

    MyBlog

    Tuesday, June 24, 2014 8:30 AM

All replies

  • Hi,

    You have configured logshpping incorrectly it seems but where I cannot guess. So please have a look at below links for similar issue

    http://ms-dba.blogspot.co.uk/2010/06/copy-and-restore-job-errors-with-log.html

    http://social.technet.microsoft.com/Forums/fr-FR/634851b4-d6e6-4f76-bfa3-5bd9dae6de77/log-shipping-copy-fails?forum=sqlreplication

    http://www.sqlservercentral.com/Forums/Topic417166-146-1.aspx

    Please revert if following above suggesstions do not help


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.

    My TechNet Wiki Articles


    • Edited by Shanky_621 Wednesday, June 11, 2014 11:06 AM
    Wednesday, June 11, 2014 10:42 AM
  • It looks like there is an issue with backup job the way it is setup.

    Select * from msdb.dbo.log_shipping_monitor_primary
    

    Run the above command and check whether all the columns are correct for server, database etc. Also take a look at the backup job step and confirm if it points to the correct server?

    HTH


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Wednesday, June 11, 2014 10:59 AM
  • Have you verified all the settings correctly ? shared location and jobs backup location ? and all the jobs? this looks like issue with your configuration.. may be issue with backup shared location

    Raju Rasagounder Sr MSSQL DBA

    Wednesday, June 11, 2014 11:48 PM
  • Please check and validate you are able to access the shared folders in bi-directional mode and Sql Server Agent Service A/C has read\write access on both of the shared location.

    Also check if you are able to access sql server from both the locations.

    what is  the db size for which you are configuring log-shipping and how important is this for you?


    Santosh Singh

    Friday, June 13, 2014 8:37 PM
  • Thank you all for your contribution.

    After testing and debugging I found that when they move their database from one server (server2) to another server (server1) the database still using the old name (server2) which you can findusing this script:

    SELECT @@SERVERNAME

    so the replication can't retrieve information, unfortunately for me it is difficult to rename the server because it sis development server so they need to make analysis about side effects if we renamed it. 


    Please Mark it as Answered if it answered your question
    OR mark it as Helpful if it help you to solve your problem
    Elmozamil Elamir Hamid

    MCSE Data Platform
    MCITP: SQL Server 2008 Administration/Development
    MCSA SQL Server 2012
    MCTS: SQL Server Administration/Development

    MyBlog

    Tuesday, June 24, 2014 8:30 AM