Re: [ADSM-L] TDP for SQL don't truncate the logs

Christian,

This is normal and correct behavior.

In the SQL Server "Full Recovery" model, in order to truncate log,
you must run a log backup.

You will see that in the Microsoft docs and the DP/SQL User's Guide.
Here is an excerpt from the Microsoft documentation:

---
     Transaction Log Truncation

          If log records were never deleted from the transaction log, it
would
          eventually fill all the disk space that is available to the
physical
          log files. Log truncation automatically frees disk space
          for reuse by the transaction log.

     Except when delayed for some reason, log truncation occurs
automatically
     as follows:

         * Under the simple recovery model, after a checkpoint.
         * Under the full recovery model or bulk-logged recovery model,
           after a log backup, if a checkpoint has occurred since the
           previous backup.
---

Thanks,

Del

----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/19/2009
08:15:36 AM:

> [image removed]
>
> TDP for SQL don't truncate the logs
>
> Christian Svensson
>
> to:
>
> ADSM-L
>
> 02/19/2009 08:16 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Hi *SMers,
> I had a lot of fun with you all at Pulse09 in Vegas. I hope I will
> see you all again at Pulse 2010 in Vegas the 24th of Feb. :)
>
> Anyway, I have a fun "problem" with a SQL 2005 Server on Windows
> 2003 running with TDP 5.5.1 x86 and TSM Server 5.4 on AIX version x.x
> But since a wild back the FULL backup that we do on SQL will not
> truncate the logs anymore, but if we do a LOG backup then will it
> truncate the logs without any issue.
> What I do see in the GUI is that the Truncate Checkbox i gray out in
> the GUI and when we choose LOG backup it is visible again but we can
> not backup all LOGs of some reason and TDP tell us that does logs
> are truncated by SQL it self's.
>
> The backups works fine and we can do restore of the databases but
> not truncate the logs without running a LOG backup after the full.
>
> I just wonder if anyone have any idea why this is happening and if
> the customer I working with has enable anything in SQL that don't
> let TSM to truncate the logs as normal?
>
> Del, do you have any idea? You are IBM's SQL/Exchange expert.