Log Shipping issues.
-
Sunday, December 23, 2012 1:22 AM
I'm setting up log shipping for 2 server that are not in domain. I've gotten to get the initial Backup and restore to the second server succesfull and the second DB goes into Stanby/Read only mode. However, the rest is not working. Btw, it took not only to change the SQL server Agent to a local user, but also changing SQL Server user to a local user as well. For some reason NT Service/MSSQLSERVER user would not be able to read the directory since it was a completely different directory.
anyhow, all 3 jobs on the secondary server are failing.
Thank you in advance for your guidance
-------------------
LSAlert - with the following error.
Log Job History (LSAlert_Monitoring_Log_ccw-stg-sql2.vpc.ccw)
Step ID 1
Server CCW-STG-SQL2
Job Name LSAlert_Monitoring_Log_ccw-stg-sql2.vpc.ccw
Step Name Log shipping alert job step.
Duration 00:00:00
Sql Severity 16
Sql Message ID 14421
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: CCW-STG-SQL2\sqluser. The log shipping secondary database AMAZONA-S2LKL4F.test has restore threshold of 45 minutes and is out of sync. No restore was performed for 4165 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed.LSCopy - with the following error.
------------------
Log Job History (LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM)
Step ID 1
Server CCW-STG-SQL2
Job Name LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM
Step Name Log shipping copy job step.
Duration 00:00:31
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: CCW-STG-SQL2\sqluser. The step failed.Log Job History (LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM)
Step ID 1
Server CCW-STG-SQL2
Job Name LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM
Step Name Log shipping copy job step.
Duration 00:00:31
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2012-12-22 20:00:31.15 *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2012-12-22 20:00:31.15 *** Error: The specified agent_id A9CB02A9-B17F-4D55-AFB4-3954B13D4242 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
2012-12-22 20:00:31.17 ----- END OF TRANSACTION LOG COPY -----
Exit Status: 1 (Error)Log Job History (LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM)
Step ID 1
Server CCW-STG-SQL2
Job Name LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM
Step Name Log shipping copy job step.
Duration 00:00:31
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2012-12-22 20:00:31.03 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2012-12-22 20:00:31.03 *** Error: The specified agent_id A9CB02A9-B17F-4D55-AFB4-3954B13D4242 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***Log Job History (LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM)
Step ID 1
Server CCW-STG-SQL2
Job Name LSCopy_ccw-stg-sql1.vpc.ccw_CCW_DM
Step Name Log shipping copy job step.
Duration 00:00:31
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2012-12-22 20:00:30.98 *** Error: Could not retrieve copy settings for secondary ID 'a9cb02a9-b17f-4d55-afb4-3954b13d4242'.(Microsoft.SqlServer.Management.LogShipping) ***
2012-12-22 20:00:30.98 *** Error: The specified agent_id A9CB02A9-B17F-4D55-AFB4-3954B13D4242 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***-----------------
LSRestore with the following error
Log Job History (LSRestore_ccw-stg-sql1.vpc.ccw_CCW_DM)
Step ID 1
Server CCW-STG-SQL2
Job Name LSRestore_ccw-stg-sql1.vpc.ccw_CCW_DM
Step Name Log shipping restore log job step.
Duration 00:00:31
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2012-12-22 20:00:30.95 *** Error: Could not retrieve restore settings.(Microsoft.SqlServer.Management.LogShipping) ***
2012-12-22 20:00:30.95 *** Error: The specified agent_id A9CB02A9-B17F-4D55-AFB4-3954B13D4242 or agent_type 2 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***
All Replies
-
Sunday, December 23, 2012 8:20 AM
I think the user account running these jobs doesnt have anough rights to update the tables in MSDB Databases.
In case you've added a monitor server also, do make sure the account has rights to update MSDB database in monitor server also.
Incase the servers are not in a domain, create a local windows login on all server with same login name and password so that the logins can impersonate and work on diff servers.
Also do make sure the login has rights on Shared directory.
Sarabpreet Singh Anand
This posting is provided , "AS IS" with no warranties, and confers no rights.
Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.
-
Monday, December 24, 2012 12:13 AMthe user running the jobs has administrator rights on both servers. same for the share. The fact that i was able to run the initial backup/restore tells me it doesnt have any issues getting to the box.
-
Monday, December 24, 2012 8:22 AMModerator
Hi Ogie,
By definition, message 14421 does not necessarily indicate a problem with Log Shipping. This message indicates that the difference between the last backed up file and last restored file is greater than the time selected for the Out of Sync Alert threshold.
There are several reasons why the alert message is raised. For the solution, please refer to http://support.microsoft.com/kb/329133.
Thanks.
Maggie Luo
TechNet Community Support -
Tuesday, December 25, 2012 6:43 PM
Thanks Maggie. The message indicates that logs are out of sync, which i know. but LScopy and LSrestore scripts are failing as well. Those are the real problems. I do think it's user permission related, however i've given admin rights to sql user and still not working.


