June 17, 2015 at 10:52 am
Hi All,
Why does the log shipping backup job he can generate the full backup file, but is failing to generate the log backups?
Anyone know what what could is going wrong?
Regards,
Antonio Estima
June 18, 2015 at 4:57 am
the log shipping backup job should be taking log backups and not full backups. Check the job step history and post here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 18, 2015 at 5:37 am
Hi thanks for your reply,
I'm sorry, I do not have detailed this issue. I have had configured log shipping with the option perform backup full and restore this backup in the secondary server. This its ok. However, after this, it is not generating bakcup log in the log shipping folder in the primary server and when we going to see the job history it don't have nothing and in the job activity monitor the backup job its active and running without generate error.
Could you help us?
Thanks,
Antonio
June 18, 2015 at 6:37 am
check the SQL errorlog, and see what this query returns
select log_time_utc,message from msdb.dbo.log_shipping_monitor_error_detail
---------------------------------------------------------------------
June 18, 2015 at 8:23 am
The just only a error happens and its after after 60 minutes without the log backup job to generate the log's backup file. Part of the error message is: "has not performed a backup log operation for 73 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed."
Before these 60 minutes the backup job don't shows us nothing error. Its running normaly and don't genarate log's backup file in the folder.
We are not using a server monitor in this log shipping configuration.
Regards,
Antonio
June 18, 2015 at 8:34 am
antonio.estima 4150 (6/18/2015)
The just only a error happens and its after after 60 minutes without the log backup job to generate the log's backup file. Part of the error message is: "has not performed a backup log operation for 73 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed."Before these 60 minutes the backup job don't shows us nothing error. Its running normaly and don't genarate log's backup file in the folder.
We are not using a server monitor in this log shipping configuration.
Regards,
Antonio
Even though its marked as successful, check the job step history carefully and post details back here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 18, 2015 at 8:46 am
Run this query on the primary, change the job name first, and post the output please
SELECT j.name
, jh.[step_id]
, jh.[step_name]
, jh.[message]
FROM msdb..sysjobs j inner join
[msdb]..[sysjobhistory] jh
on j.job_id = jh.job_id
where j.name = 'the LS backup job name here'
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 18, 2015 at 9:10 am
We are not using a server monitor in this log shipping configuration.
Regards,
Antonio
you don't need a monitor, the table is in msdb.
---------------------------------------------------------------------
June 18, 2015 at 10:28 am
I performed this query above and it did not returned nothing. However, when I filtered for job name begining with LS it returned the Job Alert History as following :
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
Regards,
Antonio
June 18, 2015 at 10:46 am
I performed this query above and it did not returned nothing. However, when I filtered for job name begining with LS it returned the Job Alert History as following:
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
Regards
Antonio
June 18, 2015 at 10:48 am
I performed this query above and it did not returned nothing. However, when I filtered for job name begining with LS it returned the Job Alert History as following:
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
LSAlert_ServerPrimary1Log shipping alert job step.Executed as user: NT AUTHORITY\NETWORK SERVICE. The step succeeded.
LSAlert_ServerPrimary0(Job outcome)The job succeeded. The Job was invoked by Schedule 41 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).
1 (Log shipping alert job step.).
Regards,
Antonio
June 18, 2015 at 10:57 am
Antonio,
have you tried the query I posted?
---------------------------------------------------------------------
June 18, 2015 at 11:10 am
Yes, I have tried.
But when I replaced 'the LS backup job name here' in clause where for the current name LS backup job, the query does not return anything.
This result is the LS alert job.
June 18, 2015 at 11:20 am
Yes, I have tried.
But when I replaced 'the LS backup job name here' in clause where for the current name LS backup job, the query does not return anything.
This result is the LS alert job.
June 18, 2015 at 1:41 pm
Hi all,
The problem was user permission, so I created a domain user and I have set up it in the service account in SQL Server agent in the two servers and I gave them full permission in the folders of the two servers, the job bakcup has performed ok.
Thanks all for your help,
Antonio
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply