Link to home
Start Free TrialLog in
Avatar of jpmoreau
jpmoreauFlag for Canada

asked on

SQL Log shipping

Hi

I have two new SQL Server in SQL SERVER 2008R2. I had activated LOG SHIPPING on my Main Database. The step LSBackup on the main server is working well. On the second server the LSCOPY step is not working. Returns with this error.

*** Error: Could not retrieve copy settings for secondary ID 'fa5f04a7-0423-41ea-b014-02ea10e681bf'.(Microsoft.SqlServer.Management.LogShipping) ***
2015-10-20 15:50:01.33      *** Error: The specified agent_id FA5F04A7-0423-41EA-B014-02EA10E681BF or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2015-10-20 15:50:01.34      *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2015-10-20 15:50:01.34      *** Error: The specified agent_id FA5F04A7-0423-41EA-B014-02EA10E681BF or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2015-10-20 15:50:01.34      *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2015-10-20 15:50:01.34      *** Error: The specified agent_id FA5F04A7-0423-41EA-B014-02EA10E681BF or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2015-10-20 15:50:01.34      ----- END OF TRANSACTION LOG COPY     -----

Is there somebody who knows how to fix this issue? I didn't find nothing onto Google.

Thanks
Avatar of Koen Van Wielink
Koen Van Wielink
Flag of Netherlands image

While not too complicated in its configuration, setting up log shipping correctly can be tricky. I learned through trial and error and needed a few attempts to get it going.
There's a question from last year that explains in detail how to set up log shipping on MSSQL 2008R2:

SQL Server disaster recovery

Have a read through the steps and follow the instructions on technet and the comments provided. If you do it in the right order, log shipping should work just fine. It's probably quicker to just reconfigure it rather than trying to repair a faulty log shipping setup.
Avatar of jpmoreau

ASKER

I had reconfigure the log shipping with all the right settings and still the same problem.
Did a quick Google on part of the error message, and others report that insufficient rights for the user that is used to run the SQL Server Agent service might be the issue. Make sure this is a domain user who has privilege on both servers.
Another reported solution has to do with the -server parameter in the copy and restore job commands. Have a look at both of these jobs, and make sure that the parameter for -server points to the SECONDARY server. Apparently sometimes this goes wrong and it points to the primary. This would be the parameter for sqllogship.exe.
What do you mean by -server
ASKER CERTIFIED SOLUTION
Avatar of Koen Van Wielink
Koen Van Wielink
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial