Lisa,

For Data Protection for SQL, you do not need to schedule
an inactivate logs. "log" backups are stored as backups,
and are inactivated automatically on the next "full"
backup of the associated database. I encourage you to read the
"Backup overview", "Backup strategies", and
"Recommended Tivoli Storage Manager policy settings" sections
of the Data Protection for SQL Installation and User's Guide
for more details.


http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmfd.doc/dpsql.htm

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/28/2008
04:27:24 PM:

> [image removed]
>
> inactivate TDP SQL transaction logs?
>
> Laughlin, Lisa
>
> to:
>
> ADSM-L
>
> 08/28/2008 04:28 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> When I setup TDP for Oracle and used RMAN jobs , the transaction logs
> were archives ( & archive deletes) and you needed to also schedule an
> RMAN job to inactivate the logs and synchronize between RMAN and
> TDP/TSM.  It's been a while and my details may be fuzzy; but it doesn't
> seem that there is an equivalent in MSSQL. And the logs are backed up,
> not archived.  Should I be scheduling inactivate jogs and do I have to
> worry about duplicate transaction log names and a limit on the number of
> versions kept for the backups of the transaction logs?  Sorry if I am
> slightly incoherent-we go live on a project over the weekend, and (as
> usual) the backups were an afterthought, so I am kind of short on sleep
> right now.  I know you guys have been there & done that.
>
> thanks!
> lisa