Yeah, OK, you've got a point.  (Too many backup products in my head
sometimes.)  I think you get the point of the test.

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of E Gold
Sent: Friday, July 27, 2007 2:03 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Performance Tuning backup

I will try this.

But if my CP is less than or equal to TS, what is the point of lowering
TS?

How long would you say to let it run before trying the next setting? 5
minutes?

Thanks alot





EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
07/26/2007 06:39:53 PM:

> I think you're going the wrong way.  And I disagree that the tape
drives
> aren't the bottleneck.  If they're LTO-2s and you're sending them
10-15
> MB/s, they ARE.  They're shoeshining like crazy.  LTO-2s want 30-35
MB/s
> times compression.  I'll assume 1.5:1, which is probably reasonable.
So
> we're looking at a target number of 45-50 MB/s (or higher if you a
> higher compression ratio.)
>
> Try these backup settings.  Each time you change the setting, try
> backing up for a while and see what you get.  DON'T RUN ANY OTHER
> BACKUPS while you're doing this.  You need all other things constant:
>
> 1. Set target sessions (TS) to one and client parallelism (CP) to one.
> 3. Set TS to 2 and CP to 2.
> 2. Set TS to 3 and CP to 3.
> 3. Set TS to 4 and CP to 4.
> 4. Set TS to 5 and CP to 5.
> 5. Set TS to 6 and CP to 6.
> 3. Set TS to 7 and CP to 7.
> And so on, and so on, until you get to 40-45 MB/s on ONE DRIVE or hit
a
> point of decreasing marginal returns (you add another stream and tput
> doesn't get any better).
>
> If you can't get to 40-45 MB/s on one LTO-2 drive (assuming you're
> getting 1.5:1 compression or more), you're not going to get there by
> adding a second drive.  You're being limited on throughput somewhere,
> and splitting that limited throughput between two tape drives will
make
> it worse not better.
>
> If you do get to 40-45 MB/s (and I don't think you will), then see if
> you can get more.  Take the number of target sessions on one drive to
n
> (the highest number you had to go to above) and the other drive this
> way:
>
> 1. Set TS to n & 1 and CP to 4.
> 2. Set TS to n & 2 and CP to 6.
> 3. Set TS to n & 3 and CP to 8.
> 3. Set TS to n & 4 and CP to 10.
> 3. Set TS to n & 5 and CP to 12.
> And so on, until you hit a point of decreasing marginal returns.
>
> Potential hold ups:
> 1. tput of the the disk that notes is on  (all RAID arrays not created
> equal)
> 2. tput of the gbE interface on the client
> 3. tput of the gbe interface on the master
> 4. tput of notes backup client
> 5. tput of the disk the client indices are on (probably not as this is
> notes and it doesn't require a lot of client index activity)
>
>
>
>
> ---
> W. Curtis Preston
> Backup Blog @ www.backupcentral.com
> VP Data Protection, GlassHouse Technologies
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
> Behalf Of E Gold
> Sent: Thursday, July 26, 2007 12:42 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Performance Tuning backup
>
> OK guys, as a test I changed my tape drive target sessions to 6 for
each
> of
> my 6 tape drives.
>
> I then changed the parallelism on the client to 12 (it used to be 8)
>
> I then noticed my server will only go up to 32 sessions for
parallelism,
> given my max is 32 are the above settings OK?
>
> Also why am I limited to 32 max?
>
> Ill see tonight if I get more speed.
>
> thanks
>
>
> ____________________________________
> This e-mail message is for the sole use of the intended recipient(s)
and
> may contain proprietary, confidential and/or privileged information.
Any
> unauthorized review, use, disclosure or distribution is prohibited.
If
> you
> are not the intended recipient (or an employee or agent responsible to
> deliver it to the intended recipient), you may not copy or deliver
this
> message to anyone. In such case, you should destroy this message and
> kindly
> notify the sender by reply e-mail.
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://listserv.
> temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

____________________________________
This e-mail message is for the sole use of the intended recipient(s) and
may contain proprietary, confidential and/or privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.  If
you
are not the intended recipient (or an employee or agent responsible to
deliver it to the intended recipient), you may not copy or deliver this
message to anyone. In such case, you should destroy this message and
kindly
notify the sender by reply e-mail.

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER