Highlighted
Rafael-Antonio Trusted Contributor.
Trusted Contributor.
239 views

MSSQL 2016 transaction log restore error

Jump to solution

Hi,

Please your help, we have successufully backups with this config:

One full daily full backup, transaction logs backup every 5 minutes and differencials every 4 hours but at the momment that we need restore to a point-in-time, fails, the strange is that only the first TL is applied, the next TL's shows the error:


The log in this backup set begins at LSN 1737000006863100001, which is too recent to apply to the database. An earlier log backup that includes LSN 1737000006862600001 can be restored

Beetween the TL's backups does not exist any backup (I guess), the DB is on Full model.

We have reviewed with the DBA and we can't find any issue, for some reason el SQL engine does not accept the LSN chain sent by Data Protector, exists some gap there.


Please your help.


Regards


Rafael

0 Likes
1 Solution

Accepted Solutions
Rafael-Antonio Trusted Contributor.
Trusted Contributor.

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hi,


The problem was resolved, on this link exists a SQL script that helped us to identify the LSN requiered by DP. The problem was a VEEAM PoC, that VM's has bee not erased and were causing interference.

https://www.dbrnd.com/2016/10/sql-server-script-to-find-all-backup-history-information-to-sync-problem/

 

Regards

RG

View solution in original post

0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hello @Rafael-Antonio,

As restore issues are usually urgent I recommend working with support (use a high priority during case creation). What Data Protector version are you running on the Cell Manager and client? Is this a standalone MSSQL, failover cluster or AO configuration?

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hello @Rafael-Antonio

I have made some research about this error and saw the same situation in DP 9.09 failing in the restore with this message. 

If you have Availability Group Databases, you should have separate backups than the standalone databases. Also for the transaction logs, backups should be different. Remember that you need to use the virtual name of the cluster to configure the Availability Group backups. 

Is that your situation? 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Rafael-Antonio Trusted Contributor.
Trusted Contributor.

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hi, thanks for your response.

Our Data Protector is 10.40, the DB is standalone, we don't any Availibity Group, is a very basic DB's.


Also, we have 2 jobs: one for FULL+DIFF and another job for TRANS, all scheduled on DP Advanced Scheduler.

We don't find where the LSN inconsistency is ocurring.

Wating your responses.

Regards

RG

0 Likes
Rafael-Antonio Trusted Contributor.
Trusted Contributor.

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hi,


The problem was resolved, on this link exists a SQL script that helped us to identify the LSN requiered by DP. The problem was a VEEAM PoC, that VM's has bee not erased and were causing interference.

https://www.dbrnd.com/2016/10/sql-server-script-to-find-all-backup-history-information-to-sync-problem/

 

Regards

RG

View solution in original post

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: MSSQL 2016 transaction log restore error

Jump to solution

Hello

This issue could happen if any of transaction or differential is overlapped with full backup. You can try to use omnirc variable for to restore in a different way.

1º Please edit omnirc file into SQL server

2º Add following variable

OB2_TIME_BASED_RESTORECHAIN=1

3º Try restore again.

 

Best Regards

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.