LSAlert job fails in job activity monitor in both DC & DR (Primary & secondary) servers in logshipping

Question

Post reply

LSAlert job fails in job activity monitor in both DC & DR (Primary & secondary) servers in logshipping

naga.rohitkumar

SSCertifiable

Points: 5738
More actions
September 3, 2012 at 3:07 am

#261327

HI,
1. LSAlert job fails in job activity monitor in both DC & DR (Primary & secondary) servers in logshipping
2. While manualy executing it is failing and msg in hisroty is "[[r] database] has backup threshold of 60 minutes and not performed a backup log operation "
3. Except this all my LSBackup jobs and LSCopy & LSRestore jobs are executing succes fully
4. In which conditions this type of issue comes and how to get reid of this and make the alerts working properly in both DC & DR
Thanks & regards
NAGA.ROHITKUMAR
Thanks
Naga.Rohitkumar

Viewing 11 posts - 1 through 10 (of 10 total)

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

Ant-Green SSC Guru Points: 113507 More actions · Answer 1

What is the frequency of your backups, copies and restores?

naga.rohitkumar SSCertifiable Points: 5738 More actions · Answer 2

HI, Anthony

Its 5mins for each

1. same issue came early for two database at that time i performed manaul Full backup using GUI and restore in secondary with (leave the database in read-only mode)

2. later i executed manualy LSbackup job in primary and LScopy and LSrestore in secondary

3. refresh the primary and secondary then issue solved and the LSAlerts in Primary and Secondary excuting normaly "I don't know this is correct or not but it happend"

4. ivl monitor for some more time if the same continues ivl reconfigure the logshipping

5. but before that i want to know the actuall technical reason for this ,It may happen again in future its not right to reconfigure logshipping always

Thanks&Regards

NAGA.ROHITKUMAR

Thanks
Naga.Rohitkumar

Perry Whittle SSC Guru Points: 234013 More actions · Answer 3

naga.rohitkumar (9/3/2012)
HI,
1. LSAlert job fails in job activity monitor in both DC & DR (Primary & secondary) servers in logshipping
2. While manualy executing it is failing and msg in hisroty is "[[r] database] has backup threshold of 60 minutes and not performed a backup log operation "
3. Except this all my LSBackup jobs and LSCopy & LSRestore jobs are executing succes fully
4. In which conditions this type of issue comes and how to get reid of this and make the alerts working properly in both DC & DR
Thanks & regards
NAGA.ROHITKUMAR

Although the jobs are marked as executed successfully, thoroughly check the output for each step of each job, you'll likely find there are some errors. Post detail of these for us to help you further

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

naga.rohitkumar SSCertifiable Points: 5738 More actions · Answer 4

HI,

As u mentioned i checkd the logs in sqlserver and event viewer

even after all jobs are executed success fully i got this mesage

the error message is : Logshipping secondary database has restore threshold 45 minutes and it is out of sync.no restoer was performed 2464 minutes. Restore latency is 10 minutes

Thanks & regards

NAGA.ROHITKUMAR

Thanks
Naga.Rohitkumar

Ant-Green SSC Guru Points: 113507 More actions · Answer 5

are you setting the force disconnect of users on the restore to ensure that the database can be restored, otherwise if a user is connected to the database SQL cannot restore the log.

Perry Whittle SSC Guru Points: 234013 More actions · Answer 6

naga.rohitkumar (9/3/2012)
HI,
As u mentioned i checkd the logs in sqlserver and event viewer
even after all jobs are executed success fully i got this mesage
the error message is : Logshipping secondary database has restore threshold 45 minutes and it is out of sync.no restoer was performed 2464 minutes. Restore latency is 10 minutes
Thanks & regards
NAGA.ROHITKUMAR

For some reason logs are not being restored. Anthony has already provided one reason, are you taking log backups outside of the LS plan.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

naga.rohitkumar SSCertifiable Points: 5738 More actions · Answer 7

Hi,

I did not set any force disconnect of database or users actualy iam practicing DC - DR drill(switch over and switch back ) in my laptop to gain knowledge

In my company mostly logshipping with cluster is in use among them one server is having DC-DR i configured same in my laptop

Thanks
Naga.Rohitkumar

Perry Whittle SSC Guru Points: 234013 More actions · Answer 8

please check the rssults of the following query when executed against your secondary database and post them back

exec sp_help_log_shipping_secondary_database

@secondary_database = 'secondary_database'

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

naga.rohitkumar SSCertifiable Points: 5738 More actions · Answer 9

HI,

as u said earlier the logs are not restored for one database sothat the LSAlert job failed in both primary and secondary

i have checkd the same and reconfigured the logshipping now its working

thanks for ur immense support iam following this site daily it is a platform to gain knowledge and clear doubts who wont say to us but we are getting solutions in 5mins through sqlservercentral

Thanks & Regards

NAGA.ROHITKUMAR

Thanks
Naga.Rohitkumar

Perry Whittle SSC Guru Points: 234013 More actions · Answer 10

you're welcome

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉