January 30, 2012 at 3:46 pm
Hello All,
New to the LS. I have created log shipping from primary to the secondary server (both servers the same specs and running SQL Server 2008R2).
I have followed the standard settings:
- primary db backup to the separate server [file server]
- copy from that location to the destination server, transaction log (trn files)
- restore to the destination server
backup and copy - every 15 min, restore is delayed by 60 min
I have setup email alert if no restore occurs within 200 min
All was working fine for the first 200 min 😉
After that I am getting alert that restore did not occur check agents jobs.
Checked both server, location paths (all paths location are accessible on the network).
Backup files are created fine, copy operation is working fine, restore is working fin, files are in its folders. All seams to be fine but when I was troubleshooting msdb.dbo.logshipping_secondary_databases using:
SELECT secondary_database, last_restored_file
FROM msdb.dbo.log_shipping_secondary_databases
Last_restored_file column is giving m NULL value where is should give me unc path to the last trn file for restore
Q: is there any way to update that table? I could probably manually point to that file since it is there and working but from what I found out this should not be updated manually this needs to be done vie proper update. So if anybody knows how to correctly update secondary db I would appreciate for any pointers.
Regards
Kris
btw. no errors on either server or agents jobs - all on green, when I run all three tasks on its own all succssfull
Current Error via email:
DESCRIPTION:The log shipping secondary database <server.db_name> has restore threshold of 200 minutes and is out of sync. No restore was performed for 225 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
January 31, 2012 at 5:29 am
Are you using a seperate server as the monitor? It sounds like your secondary server is not updating the monitor correctly. This could be a permissions issue or comms etc.
January 31, 2012 at 5:39 am
sounds to me like your restore job is running but actually has no logs to restore. Check the history for the restore job and confirm by checking the errorlog for any reports that a log has been restored.
---------------------------------------------------------------------
January 31, 2012 at 6:03 am
Thank you very much for the response.
Had to act quick on this one.
Early this morning decided to scrap the logShipping configured yesterday and start from the scratch.
Broke down the LS on the primary
Removed pointer to the secondary on the LS configuration
Disabled Log Shipping on the primary
Tried bring the database on the secondary to online status [Restore <dbname> with recovery] (no joy - was getting error db is in use)
Took DB ofline
Delere DB
After that:
moved backup files on the backup server to the temp_old folder
on the secondary server moved files to the temp folder as well (trn files copied from the backup server)
Setup brand new logShipping creating new DB on the secondary, made sure all the paths are proper UNC paths
and so far so good
As I delay restore by 60 min I have checked LS again using query:
SELECT secondary_database, last_restored_file
FROM msdb.dbo.log_shipping_secondary_databases
and now under last_restored_file I got proper value (were previously I had NULL)
So far no alerts and files are backuped/copied and restored correctly
January 31, 2012 at 6:11 am
arrnvid (1/31/2012)
Tried bring the database on the secondary to online status [Restore <dbname> with recovery] (no joy - was getting error db is in use)
Hmmm, I wonder if that was the issue with the log restores?
Thats a good process to follow when redoing log shipping, save your tranlogs off elsewhere, don't delete them.
don't forget to come back and delete them later!
---------------------------------------------------------------------
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply