SQL Log Restore Failure

[NBU_NEWBIE]

Hi

We recently started backing up one of MS SQL 2008 R2 databases with Netbackup 7.0.1. All seemed ok till we decided to do a point in time recovery exercise. We managed to restore the database ok but log restore fails.

Method of restore is:

- Create a move template. Picked up a random time from the list of backups with following options selected. 1) Stage fill recover 2) Recovery type - Recovered 3) Transaction Log Recovery Option - Point In Time

- Edited the batch file by removing the hashes and started the job.

As I mentioned earlier, database is restored ok but the logs don't get restored. Due this the database is shown as "recoverying" (Restore was done to test server). Following 2 error messages appear

1)

DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <4326><[Microsoft][SQL Native Client][SQL Server]The log in this backup set terminates at LSN 719022000004454600001, which is too early to apply to the database. A more recent log backup that includes LSN 719022000004462100001 can be restored.>.
DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]RESTORE LOG is terminating abnormally.>
ERR - Error found executing <restore log "databasename" from VIRTUAL_DEVICE='VNBU0-3168-3548-1287636854' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery>.
ERR - Internal error. See the dbclient log for more information.
ERR - Error in VDS->Close: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\testrestorebatch FAILED with STATUS 1 (0 is normal). Elapsed time = 23(0) seconds.
ERR - Error in GetCommand: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\testrestorebatch>:
<1> operations succeeded. <1> operations failed.
ERR - Error in DBthreads::dbclient: 6.
    CONTINUATION: - The system cannot find the file specified.
ERR - Error in VxBSAEndData: 6.
    CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.

2)

21/10/2010 5:54:47 p.m. - restored image IMAGENAME_1287555490 - (the restore failed to recover the requested files(5)); restore time 00:00:30
21/10/2010 5:54:50 p.m. - end Restore; elapsed time: 00:00:35
the restore failed to recover the requested files(5)
21/10/2010 5:54:52 p.m. - Error bpbrm(pid=8236) client restore EXIT STATUS 5: the restore failed to recover the requested files

 Occassionally this error also pops up

21/10/2010 2:57:32 p.m. - Error bpbrm(pid=1872) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
21/10/2010 2:57:32 p.m. - restored image IMAGENAME_1287555490 - (file read failed(13)); restore time 00:00:19
21/10/2010 2:57:37 p.m. - Error bpbrm(pid=1872) client restore EXIT STATUS 13: file read failed    
21/10/2010 2:57:37 p.m. - end Restore; elapsed time: 00:00:25
the restore failed to recover the requested files(5)

Additional infor about the backup policies.

There are separate policies. 1 for db backups and 4 for logs. (separate schedules under one policy didnt work so we created 4 separate policies to backup logs every 15 minutes.

Has anyone had similar issues? Any help on resolving this issue will be great.

Thanks

Marcus

[Zahid_Haseeb]

Would you please share the SQL logs ?

[Zahid_Haseeb]

Try the below both links. it may help you hopefully

http://www.symantec.com/business/support/index?page=content&id=TECH16981

https://www-secure.symantec.com/connect/fr/forums/sql-database-failure

[Marianne]

1. The log in this backup set terminates at LSN 719022000004454600001, which is too early to apply to the database. A more recent log backup that includes LSN 719022000004462100001 can be restored.
2. ERR - Internal error. See the dbclient log for more information.

Have you tried to restore from a 'more recent' backup?

Do you have dbclient log directory on the destination client?

[NBU_NEWBIE]

Marianne, dbclient log basically shows what I have posted above, however I am happy to attach the log file if it helps identify the problem. Also yes I have tried to restore from most recent backup and it still fails..

Zahid, I will go through the articles today..

Thanks

Marcus

[Zahid_Haseeb]

Check few things as well

1.) Space on the target Server where your  restore activity is failing( Space should be double from the database size backup )

2.) Reduce/shrink the size of your LOG files of SQL (are they much big ?)

3.) Before restoring the SQL backup make sure there must not be a database already in recovering .. if yes then should remove the database from SQL if they are in recovering and then go for restore.