ADSM-L

Re: [ADSM-L] TDP Sql question about log growing

2009-01-23 08:15:19
Subject: Re: [ADSM-L] TDP Sql question about log growing
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 23 Jan 2009 08:14:01 -0500
Hi Paul,

Yes, Data Protection for SQL can run log backups.
Please read the User's Guide for details.

It does not run the "DBCC SHRINKFILE" command.
Many customers want control over when that happens,
so they schedule this within their normal SQL Server maintenance windows.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/22/2009
10:14:11 PM:

> [image removed]
>
> Re: TDP Sql question about log growing
>
> Paul Dudley
>
> to:
>
> ADSM-L
>
> 01/22/2009 10:15 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Can that log backup be run within TDP Sql or does it have to be run
> using MSSQL?
>
> Thanks & Regards
> Paul
>
> Paul Dudley
> Senior IT Systems Administrator
> ANL Container Line Pty Limited
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Del Hoobler
> Sent: Friday, 23 January 2009 1:38 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TDP Sql question about log growing
>
> Robert,
>
> You need to run a LOG backup in order to truncate the logs.
>
> BTW, truncating the transaction log does not reduce the size of a
> physical log file; it reduces only the size of the logical log file.
> To reduce the size of a physical log file, it is necessary to shrink the
> file,
> using, for example, the DBCC SHRINKFILE command.
>
> Here is an IBM Technote that discusses it:
>         http://www-01.ibm.com/support/docview.wss?uid=swg21199294
> If you want real deep details, look here:
>         http://msdn.microsoft.com/en-us/library/ms190440.aspx
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/22/2009
> 03:31:10 AM:
> > TDP Sql question about log growing
> >
> > Robert Ouzen Ouzen
> >
> > to:
> >
> > ADSM-L
> >
> > 01/22/2009 03:32 AM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Please respond to "ADSM: Dist Stor Manager"
> >
> > Hi to all
> > In a sever Windows 2003 with  SQL database I saw that a log increase
> > very much ( to +26 GB) , it was programmed  with the option Recovery
> > Model:  Full
> >
> > I run every day a full backup (not any log backup) with the command:
> >
> > tdpsqlc backup * full /tsmoptfile=%sql_dir%\dsm.opt /logfile=%
> > sql_dir%\sqlfull.log >> %sql_dir%\sqlsched.log
> >
> > I add those lines in my dsm.opt:
> >
> > INCLUDE "\...\meta\...\*"     mgwhighlearnf
> > INCLUDE "\...\data\...\*"      mgwhighlearnf
> >
> > If I understand correctly the full backup truncate the log after it
> > finish ??? In my case running just full backup I can turn it to just
> > Recovery Model:  simple
> >
> > But just for knowledge why the full backup did not clear the log ?????
> > I first turn the Recovery Model to: simple to run a shrinking
> > procedure (turn the log to 10MB).
> >
> > By the way what the difference if instead of the lines of the
> > INCLUDE I wrote previous I will write:
> >
> > INCLUDE "\...\meta\...\full*"     mgwhighlearnf
> > INCLUDE "\...\data\...\full*"      mgwhighlearnf
> > And let my recovery model to:  Full
> >
> > Did now it will truncate the log after each full backup ??????? or I
> > need to add a truncate option somewhere ????
> >
> > My TDP for SQL version is 5.2.1.0
> >
> > Regards,
> >
> > Robert Ouzen
>
>
>
>
>
>
> ANL DISCLAIMER
>
> This e-mail and any file attached is confidential, and intended
> solely to the named addressees. Any unauthorised dissemination or
> use is strictly prohibited. If you received this e-mail in error,
> please immediately notify the sender by return e-mail from your
> system. Please do not copy, use or make reference to it for any
> purpose, or disclose its contents to any person.

<Prev in Thread] Current Thread [Next in Thread>