Re: Best Practices/Best Performance SP/TSM B/A Client Settings ?

[Leandro Mazur]

Hi Tom,

One other option, if you have SQL 2008 or above, is to set "sqlcompression"
in tdpsql.cfg. In some databases we were able to reduce by half size of a
full backup.


On Fri, Mar 31, 2017 at 9:44 AM, Hans Christian Riksheim 
wrote:

> Any reason to set TCPWINDOWSIZE lower than maximum? And on the same note
> why not let the OS handle it(TCPWINDOWSIZE 0) ?
>
> Hans Chr.
>
> On Tue, Mar 28, 2017 at 9:54 PM, Matthew McGeary <
> matthew.mcge...@potashcorp.com> wrote:
>
> > Hello Tom,
> >
> > Yes, you will need a mountpoint for each stripe.  Unlike
> > resourceutilization, stripes represent client sessions that send data,
> not
> > data and control sessions combined.
> >
> > Since we're totally in the container-class pool world, all my nodes have
> > maxnummp=100 because I heavily use multiple sessions to increase
> throughput.
> >
> > __
> > Matthew McGeary
> > Senior Technical Specialist – Infrastructure Management Services
> > PotashCorp
> > T: (306) 933-8921
> > www.potashcorp.com
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> > Tom Alverson
> > Sent: Tuesday, March 28, 2017 1:43 PM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: [ADSM-L] Best Practices/Best Performance SP/TSM B/A Client
> > Settings ?
> >
> > I tried 10 and the backup failed due to not enough mount points.  I set
> it
> > to 2 and that did speed things up.  Do I need one mount point for each
> > stripe?  We normally set the mount points to 2.  Does this mean that I
> need
> > one mount point for my conventional TSM backup and 10 more to do 10
> > stripes?  I notice that when I set RESOUCEUTILIZATION to 10 for the
> > conventional backups I get four parallel sessions.  Do I need 4 mount
> > points just for that (plus whatever I need for SQL)?
> >
> > Thanks!
> >
> > On Mon, Mar 27, 2017 at 3:24 PM, Matthew McGeary <
> > matthew.mcge...@potashcorp.com> wrote:
> >
> > > If you're using TDP for SQL you can specify how many stripes to use in
> > > the tdpo.cfg file.
> > >
> > > For our large SQL backups, I use 10 stripes.
> > >
> > > __
> > > Matthew McGeary
> > > Senior Technical Specialist – Infrastructure Management Services
> > > PotashCorp
> > > T: (306) 933-8921
> > > www.potashcorp.com
> > >
> > >
> > > -Original Message-
> > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> > > Of Tom Alverson
> > > Sent: Monday, March 27, 2017 1:11 PM
> > > To: ADSM-L@VM.MARIST.EDU
> > > Subject: Re: [ADSM-L] Best Practices/Best Performance SP/TSM B/A
> > > Client Settings ?
> > >
> > > Our biggest performance issue is with SQL backups of large databases.
> > > Our DBA's all want full backups ever night (and log backups every
> > > hour) and for the databases that are around 1TB the backup will start
> > > at Midnight and finish 5 to 13 hours later (varies day to day).  When
> > > these backups start extending into the daytime hours they complain but
> > > I don't know how we could improve the speed.  Our Storage servers all
> > > have 10GB interfaces but they are backing up hundreds of clients every
> > > night (mostly incremental file level backups).  I am running a test
> > > right now to see if RESOURCEUTILIZATION 10 helps one of these database
> > > backups but I suspect it will make no difference as 99% of the data is
> > > all in one DB and I don't think SQL/TSM will split that into multiple
> > streams (will it?).
> > >
> > > On Sun, Mar 26, 2017 at 6:57 AM, Del Hoobler 
> wrote:
> > >
> > > > Hi Tom,
> > > >
> > > > My original posting was an excerpt from best practices for container
> > > > pools, and does not necessarily apply to other storage pool types.
> > > >
> > > > Yes, client-side deduplication and compression options should be
> > > > avoided with a Data Domain storage pool.
> > > >
> > > > A fixed resourceutilization setting of 2 may underperform for
> > > > clients that have a lot of data to back up and fast network
> > > > connections, but this is not a black and white answer. There are
> > > > various other conditions that can affect this and trying to narrow
> > > > in on them in
> > > ADSM-L would be difficult.
> > > > If you want some help with a performance issue, please open a PMR.
> > > >
> > > >
> > > > Del
> > > >
> > > > 
> > > >
> > > > "ADSM: Dist Stor Manager"  wrote on 03/25/2017
> > > > 12:20:43 AM:
> > > >
> > > > > From: Tom Alverson 
> > > > > To: ADSM-L@VM.MARIST.EDU
> > > > > Date: 03/25/2017 05:40 AM
> > > > > Subject: Re: Best Practices/Best Performance SP/TSM B/A Client
> > > > > Settings
> > > > ?
> > > > > Sent by: "ADSM: Dist Stor Manager" 
> > > > >
> > > > > Del:
> > > > >
> > > > > We have been using these settings as our defaults.  Is our
> > > > > TCPWINDOWSIZE too large?
> > > > >
> > > > 

delete filespace on replicated node

[Paul van Dongen]

Hi Spectrum Protect experts,

Anyone who has done a DEL FILESPACE on a replicated node? We are using PROTECT 
STG + REPLICATE NODE to protect some of our SP for VE nodes. We receive lots of 
requests from our customers to delete backups of VMs that were deleted, and 
today we ran (for the first time) a DEL FILESPACE (on the source server) for 
some VMs. The filespaces are however still present on the target server, after 
REPLICATE NODE FORCERECONCILE=YES and EXPIRE on both sides.

Any thoughts? If this is the expected behavior we will have to adapt our 
scripting in order to delete the filespaces on both servers.

Kind regards,
Paul van Dongen