Log Shipping Copy Fails

  • I am trying to implement Log Shipping across several SQL Server 2005 systems. My goal is to have one primary and probably four secondaries. I set up the primary and the 1st secondary and everything worked as promised. However, with the 2nd secondary, the transaction log copy to the secondary fails with the following:

    Message

    2008-07-21 16:00:02.85*** Error: Could not retrieve copy settings for secondary ID 'b135549e-76d8-4297-a5b3-b043a01267ac'.(Microsoft.SqlServer.Management.LogShipping) ***

    2008-07-21 16:00:02.85*** Error: The specified agent_id B135549E-76D8-4297-A5B3-B043A01267AC or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***

    2008-07-21 16:00:02.87*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***

    2008-07-21 16:00:02.87*** Error: The specified agent_id B135549E-76D8-4297-A5B3-B043A01267AC or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***

    2008-07-21 16:00:02.87*** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***

    2008-07-21 16:00:02.87*** Error: The specified agent_id B135549E-76D8-4297-A5B3-B043A01267AC or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***

    Is there something different for configuring subsequent secondaries? I set it up exactly the same as the first, including the agent accounts.

    Any thoughts. Thank you.

  • Found the problem. You cannot add a 2nd secondary without deleting the 1st secondary and the primary . . . and starting all over again. You must do them all at once. Therefore, if I want to add a 3rd secondary, I will have to blow everything away, configure the primary and then all 3 secondaries. Oh well. :w00t:

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply