September 5, 2012 at 2:06 am
i have two test log shipping servers set up. both going to different secondaries but using the same backup location and monitoring server..
Both are working, i get no errors and can look on the secondaries and see up to date info for the last backups.
So why in msdb tables. does one have NULLs for restored_file and date
SELECT secondary_database,
last_restored_file,
last_restored_date
FROM msdb.dbo.log_shipping_secondary_databases
NULLS in
SELECT primary_database ,
last_copied_file ,
last_copied_date ,
last_copied_date_utc ,
last_restored_file ,
last_restored_date ,
last_restored_date_utc ,
last_restored_latency
FROM msdb.dbo.log_shipping_monitor_secondary
for everything except last_restored_date and last_restored_date_utc
But the other has all those details filled in.
Hope someone can help.
// EDIT
I decided to remove the log shipping that was having NULLS (I dont have NULLS anymore.. Any ideas what i did to cause that???)
Also can you only have one log shipping DB monitored by a instance? I give each db monitor job a different name but Its just replaced the old monitoring job for the other db.. (didnt notice before) I cant see any reference in BOL.
September 5, 2012 at 3:53 am
nulls would indicate that although the backup and copy are running no logs are being restored, there can be many different reasons why this happens.
Carefully check the job step history for the restore job
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 5, 2012 at 6:30 am
thanks Perry ill take a look.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply