MS SQL Module Recover from an older full db backup

[wickd]

Hello,

it seems that the Legato SQL Modul has a very big bug.

When you do SQL backup's without the Legato BSM Module and you backup both the database and the transaction logs then you can restore an old DB Backup and restore all transaction log backups in sequense to recover from this old db backup to now. But if you try this with the BSM Module from legato the only way to restore the db is to recover the most recent db full backup. If you try to recover from a older full backup you can only restore the inc (log backups)between the older full and an newer full backups.
In my case the db from our custermer is corrupt and the only way to restore the database is to restore a version without corruption and do a recover with transaction log backups to now. And thats the problem: With the BSM Module its only possible to retore the most recent full backup.
Had anyone the same problem?


Without the BSM Module you can do the following:
For example, assume the following sequence of events:

8:00 A.M.
Back up database
Noon
Back up transaction log
4:00 P.M.
Back up transaction log
6:00 P.M.
Back up database
8:00 P.M.
Back up transaction log
10:00 P.M.
Failure occurs

Restore the database using an earlier database backup (earlier than the last database backup created).
Create a backup of the currently active transaction log.

Restore the 8:00 A.M. database backup, and then restore all four transaction log backups in sequence. Do not restore the 6:00 P.M. database backup. This rolls forward all completed transactions up to 10:00 P.M.
This process will take longer than restoring the 6:00 P.M. database backup.

Beest Regards

Dieter

 

[speculos]

Hello Dieter,

I successfully recovered a SQL2000 Database using the transaction log with Networker Module 3.1.1: you have to specify the exact date/time you want BEFORE you browse the index.

Version of SQL Module of Networker?
Version of SQL Server?

 

[wickd]

Hello ,

that 's not the question. Have you ever restored an full backup that was older then the last full backup and have than applied all transactions logs between the older full backup and the newest transaction log backup ? Please read the example from the MS SQL Technet about the recover.

Greetings

Dieter

 

[speculos]

Yes, I did that; The Networker module will do what you want:
you have to specify a date/time before the last full save, and Networker will restore the previous full (With no recovery), and then automaticly apply the log.
You don't have to do it manually. See "Point in Time Restore" in the "Networker Module for SQL Administrator's Guide".

 

[wickd]

Hallo,

onsemore, for example you do Mo trough Fr. a full backup
at 01:00 AM and you do Mo throug Fr at 1 PM an inc. backup (transaction log backup). Eeach backup type is stored on different tapes.
Now its Friday 3 PM and you lost your database. Then you recognize that the tapes with your full backup are damaged. The only tape you have is the full backup from Mo. 1 AM and the log backups from each day.
In this case is it not possible to recover the full backup from Monday and do a point in time recover to Fr. 3 PM.

This happend to one of our customer and the statement from Legato is, you can only recover the most recent full backup and apply the transaction logs after this backup. Is it not possible to recover the Mo full Backup and go ahead to Friday.

Greetings Dieter

 

[milanvo]

Hi Dieter,

if I understand correctly, you have backups like this :

Mo - full incr
Tu - full incr
We - full incr
Th - full incr
Fr - full incr

And you want restore for example full backup from monday and then replay logs from following days.

When you use point-in-time recovery in NW module for SQL, by default it recover most recent full backup and then replay logs.

Only way (to my knowledge) to do it, is avoid Networker to use unwanted full backups. Try change full-level savesets status to suspect, or delete it from media database - see NSRMM manual.

Deleting savesets removes records from media database permanently ! Only way back is restore media database, or scan tapes...