Manual Transaction Log Backup Even in Same Path Will Break Log shipping

Manual Transaction Log Backup Even in Same Path Will Break Log shipping 

Description:

Manual log backup or using Maintenance Plan taking Transaction log backup @ primary even in same path or different path is causing Transaction log shipping to fail. 

Solution:

we should need to manually restore Transaction log backup of  that file to resolve then later we should need to disable log backup or we should need to exclude database on maintenance plan @ primary

Here I am going to give Demo

Primary: User-PC\MSSQL2012Source

Secondary:1 User-PC\MSSQL2012DESTSQL

Secondary 2: User-PC\SQL2012CONVTEST

Log shipping Database: Testdbgrowth

Primary: User-PC\MSSQL2012Source

Secondary:1 User-PC\MSSQL2012DESTSQL

Secondary 2: User-PC\SQL2012CONVTEST

Transaction log backup Job info @ Primary

Transaction log path info @ primary

it is same path for already we configured log shipping on primary

we can see after Run transaction log backup we got file same path as see below

After we ran copy job and trying to restore we got job failed

Error giving more info as this transaction log backup maintenance plan file can not restore it is too recent to apply even in same path

Even in report give info as it copied before transaction log backup as see below

To resolve this issue

we should need to restore manual as Transaction log backup maintenance plan file as see below

you can see we got successfully restored manually

we got restore success as after running job manually

we also find from report file latest file copied as see below

we can confirm via jobs as see below

so we should need to disable transaction log backup

or we should need to exclude log shipping involving database on primary 
as see below

That is it Keep Blogging!!!!!!!!!!!!!!!!!!!

Happy Teachers Day 2017!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!