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

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=