In performing backups, the SQL Server simply gives DP/SQL a stream of
bytes.
The DP/SQL code is not told which files these bytes are from, it is
simply a stream of bytes. At restore time, DP/SQL hands the stream of
bytes
back to the SQL Server, and the SQL Server writes those bytes to files.

However... one possible way to do this is to perform the restore of
the database and logs into a DIFFERENT database name and DIFFERENT
location,
and choose the option to NOT run recovery. This will restore the .MDF and
.LDF
files into a separate location. You can then do what you want with the
files.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/08/2009
08:10:32 AM:

> [image removed]
>
> MS-SQL TDP log restore question
>
> Zoltan Forray/AC/VCU
>
> to:
>
> ADSM-L
>
> 10/08/2009 08:11 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> My MS-SQL guy has the following question and was hoping some TDP experts
> can give us an answer, one way or the other:
>
>
> "We have an issue that may require physically looking through an old
> transaction log backup to see if we can find out some information about
> who is doing what in the database.  However, since the TDP client takes
> the backups straight off to TSM, I'm not sure how to do that.  Is there
a
> way we can pull those transaction log backups out of TSM and put them on
> the server as a file as opposed to doing a restore? "