Netbackup interfering with SQL server log shipping/replication

Question

Hi

We currently have Netbackup configured on our Production database and we can thereby shrink the logfile size so it does not keep growing. 

We are now enabling log shipping on our primary db so that we can replicate the data to another server. We noticed that with that enabled there is backup happening via log shipping besides the netbackup scheduled earlier. so when we try to restore the log shipping backup to other location, we get this error

2019-11-19 04:45:20.92    *** Error: The file ‘\\LVSP10SQL001\LS_backup\Account_20191119043017.trn’ is too recent to apply to the secondary database ‘Account’.(Microsoft.SqlServer.Management.LogShipping) ***

2019-11-19 04:45:20.92    *** Error: The log in this backup set begins at LSN 74337000001428600001, which is too recent to apply to the database. An earlier log backup that includes LSN 74337000001366400001 can be restored.
RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) **

Could you advise what are the various ways to overcome this ?

Thanks

RG

Answer 1

Hi RajGulati,

According to your error message, your issue is that the LSN did not match. Usually, taking a backup changes the database and affects how later backups are restored. A copy-only backup is a SQL Server backup that without affecting the overall backup and restore procedures for the database. But it is used for a special purpose. A database can only have one backup plan. Or some issues will occur as yours. Log shipping can also looks like a method  for database backup.  

Best regards,
Cathy 

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact [e-mail]