August 16, 2010 at 3:45 pm
Hello Everyone
I am fighting the configuration of SQL Log Shipping between two boxes. These boxes are on opposite sides of the country, in different time zones. The Primary on the east coast and the secondary on the web coast. Everything that I have tried has failed. I cannot get the secondary to every restore the log backups. I have set up the monitor database, to use the secondary database. All the tables are empty. The SQL jobs are failing, with no good reason why.
Here are the only messages that I have from the job steps:
2010-08-16 14:30:16.40*** Error: Could not retrieve copy settings for secondary ID 'adbed5dc-6dc4-49f5-8c25-5eadbc81858b'.(Microsoft.SqlServer.Management.LogShipping) ***
2010-08-16 14:30:16.40*** Error: The specified agent_id ADBED5DC-6DC4-49F5-8C25-5EADBC81858B or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2010-08-16 14:30:16.41*** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2010-08-16 14:30:16.41*** Error: The specified agent_id ADBED5DC-6DC4-49F5-8C25-5EADBC81858B or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2010-08-16 14:30:16.41*** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2010-08-16 14:30:16.41*** Error: The specified agent_id ADBED5DC-6DC4-49F5-8C25-5EADBC81858B or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
I have followed the steps in the SQL BOL to the letter.
Can anyone decipher these messages?
Thanks
Andrew SQLDBA
August 16, 2010 at 4:02 pm
Andrew, a google of that error suggests permission issues. Are the SQL services on the secondary running under a domain user account that has sufficient privileges on the primary server?
---------------------------------------------------------------------
August 16, 2010 at 4:32 pm
HI George
Yes, the AD accounts are the same on both boxes. Right now for the troubleshooting, I have granted the accounts on both boxes to the admin level permission level.
I have a path that I am going down now. I found something in the SQL BOL, I will post the results if it works. Waiting until the job fires it off again.
Andrew SQLDBA
August 17, 2010 at 2:52 am
and the service account shud have same level of permissions on the network share as well..
Rohit
August 17, 2010 at 8:35 am
Yes, both account have the same level permission.
Anything else to look at?
Andrew SQLDBA
August 17, 2010 at 1:04 pm
Please execute the below before setting up the logshipping. With the error I am presuming there is old entries. Execute both on primary and secondary.
use msdb
go
delete log_shipping_primary_databases
delete log_shipping_primary_secondaries
delete log_shipping_monitor_primary
delete log_shipping_monitor_history_detail
delete log_shipping_monitor_error_detail
delete log_shipping_secondary
delete log_shipping_secondary_databases
delete log_shipping_monitor_secondary
delete log_shipping_monitor_alert
delete log_shipping_primaries
delete log_shipping_secondaries
If the logshipping setup is completed, for some reason the restore job is failing other things to check.
1. Backup is completed on the primary
2. Copy is done on the secondary
3. Restore is done on the secondary.
Please look at the job history of all the 3 processes should help you to troubleshoot the problem.
Thanks,
Ganesh
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply