Have set up an incredibly simple log shipping scenrio before tackling the real thing.
Following this doc
I restored the (very small) DB to the secondary server.
Made a file share for the log backups on the primary.
No witness/monitor involved here.
Stepped through the LS wizard and set schedules.
I looked at the folder on the secondary server and the trn files are being copied across every 5 minute as should. Restore is not happening.
I checked the error log and found that the secondary DB was not in norecovery or stand by mode.
I restored the secondary DB again and left it in stand by mode.
Everything looks like it should be fine.
None of the data changes I made in the primary show in the secondary.
When I check the sql error logs I see...
The log shipping secondary database xxx.xxx has restore threshold of 45 minutes and is out of sync. No restore was performed for 162 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information
I see no clues in the agent log on either server and there is no monitor.
Could this be a side effect of the secondary database being not norecover or stand by when I first setup LS?
Or is it because the secondary DB is currently showing standby/read only?
and if so why, the doco says it should be in standby mode