SQL Server Log Shipping common errors | Log shipping failed || Log Shipping Issues. SQL log shipping

[@HolySpiritInspired]

I wish you could demonstrate the 2nd problem for the missing LSN number that’s what am facing don’t know what to do

[@michaelade9951]

Great explanation, thank you.

[@Kamal-kh6ic]

sir my log shipping at secondary server is getting failed repeatedly. The message appears like could not apply log backup file because requires an open and available connection to the source. What could be the reason behind also pls suggest the workaround for fizxing the problem sir?? I am stuck into this since 2 weeks....

[@TechandArt]

Check with network team and also check shared disk ...seems network issues .......It's looks like log backup file cruppeted during restore apply .... Check with restore verify only command abt backup files status .... also if possible remove log shipping and recreate it ...

[@manoharreddy7599]

If you explain practically that will understood better when compared to theory.(FOR ALL VIDEOS)

[@vishwateja450]

Error: Could not retrieve backup settings for primary ID '99817903-626e-4380-bcf1-c09ca6f48b6d'.(Microsoft.SqlServer.Management.LogShipping) ***. how to fix

[@narasimhaborigarla5074]

Good explanation

[@TechandArt]

Thanks dear

[@thirupathiraot2207]

Keep doing sir...

[@ramareddy6798]

Nice post sir

[@husnakowser3647]

I am getting *** Error: The log in this backup set begins at LSN 1517XXXXXX, which is too recent to apply to the database. An earlier log backup that includes LSN 1511XXXXXX can be restored in the job history and in the error log it says "The log shipping secondary database has restore threshold of 45 minutes and is out of sync. No restore was performed for 9060 minutes. Restored latency is 17 minutes. Check agent log and logshipping monitor information."

[@TechandArt]

You need to identify the missed log backup on secondary and that need to restore on secondary manually and then resume all the jobs it will take it from there automatically and it will make synced

[@vijaythakur5669]

Good explanation

[@ramareddy6798]

Nicely explained