Hi Eric,

Have you considered using the "/STRIPes=n" option?
It allows you to break up the single stream of bytes
into "n" stripes on different parallel sessions.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 02/03/2010
04:58:48 AM:

> [image removed]
>
> Re: DP for SQL Server backup file size
>
> Loon, EJ van - SPLXM
>
> to:
>
> ADSM-L
>
> 02/03/2010 04:59 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Hi Dell!
> Jus one additional question: If I cannot set a maxsize to control the
> size of a DP for SQL backup file, how can I prevent a SQL Server backup
> from pinning the TSM recovery log?
> One of our DP for SQL clients is backing up a very large SQL database
> and it's running for several hours. Because DP for SQL is treating this
> as one single transaction which is running for a long time, it's pinning
> the recovery log (a show logpinned confirms this).
> Thanks again for your help!
> Kind regards,
> Eric van Loon
>
> > Eric,
> >
> > There is no way to set a max file size for Data Protection for SQL.
> >
> > Thanks,
> >
> > Del
> >
> > ----------------------------------------------------
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 01/18/2010
> > 01:50:14 PM:
> >
> > [image removed]
> >
> > DP for SQL Server backup file size
> >
> > Loon, EJ van - SPLXM
> >
> > to:
> >
> > ADSM-L
> >
> > 01/18/2010 01:51 PM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Please respond to "ADSM: Dist Stor Manager"
> >
> > Hi TSM-ers!
> > Today and last weekend we encounted a filled recovery log on two
> > different servers. It looks like both of them were caused by a
> > pinned recoverylog. TSM started one incremental after the other, but
> > could not free up space. I had to bounce both servers.
> > I found two parameters to prevent the log from getting pinned
> > (THROUGHPUTDATATHRESHOLD and THROUGHPUTTIMETHRESHOLD) but I found no
> > recommended values...
> > Another document talks about limiting the size of files written to
> > the diskpool. Large files written to a fragmented diskpool tend to
> > pin the log too. I know my SQL clients are the only clients writing
> > very large backup files. I cannot find a DP for SQL Server parameter
> > to tune this. I know you can set the file size in the DP for Oracle
> > and SAP client. Is this also somehow possible in the SQL Server
> client?
> > Thanks in advance for any reply!
> > Kind regards,
> > Eric van Loon
>
>
>
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee
> only. If you are not the addressee, you are notified that no part
> of the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
> and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor
> responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> **********************************************************************