December 17, 2011 at 12:02 am
Log are been backed up every 15 mins on primary server & same is copied and restored on DR server every 15 minutes.
But in MSDB database(Primary server)-the table log_shipping_monitor_primary is showing the last backup file of 7 hours ago.Due to this alert job is getting failed on primary server.
MSDB database(Secondary server)-the table log_shipping_monitor_secondary is showing latest copied & restored files which are physically visible on Primary server.
Physically on the primary server i can see the latest log backup & the same is copied & restored on DR server.
PLEASE HELP!!!!!!!!!
December 17, 2011 at 1:15 am
Please verify Log shipping status. Is it disabled? Do you find any errors in Logs for Log Shipping?
December 18, 2011 at 5:49 am
December 21, 2011 at 2:13 pm
Probably a little too obvious but is your log shipping restore sql job on the Secondary Server enabled (obviously the ls copy is). If it is enabled, is it failing? And if so, what is the message?
December 21, 2011 at 4:01 pm
mahesh.dasoni (12/17/2011)
Log are been backed up every 15 mins on primary server & same is copied and restored on DR server every 15 minutes.But in MSDB database(Primary server)-the table log_shipping_monitor_primary is showing the last backup file of 7 hours ago.Due to this alert job is getting failed on primary server.
MSDB database(Secondary server)-the table log_shipping_monitor_secondary is showing latest copied & restored files which are physically visible on Primary server.
Physically on the primary server i can see the latest log backup & the same is copied & restored on DR server.
PLEASE HELP!!!!!!!!!
check the history for the copy and restore jobs to ensure they have done something, I.E. message indicating 1 file copied or 1 file restored. The job will report successful even if it hasnt done anything, it sounds very much like you have a missing log backup file.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 22, 2011 at 2:55 am
If problem still exist then reinitialize logshipping at secondary server.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply