Thanks Vernon.

I'm not actually having a problem, I'm trying to figure out how many
LTO-4 drives a T2000/T5220 could keep streaming while pulling data off
of a staging area.

Though this looks like something I should look into.

Thanks!

Joel

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Vernon Harris
Sent: Monday, October 12, 2009 8:41 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Sun Hardware

Joel,
Take a look at this tech note.  Looks like there is a bug in 7.5 that
maybe causing your slowness.


Posted: Sun Jun 14, 2009 10:25 pm    Post subject: Re: cloning very slow
in Networker 7.5.1   

________________________________
 
If
you are running on Solaris, there is a known issue (starting in 7.5.x)
that is causing slowdowns in all cloning. The release notes stated
this, on page 46... 


Quote: 

Solaris 9 users who upgrade from NetWorker 7.2.x may notice errors
during 
cloning operations 
LGTsc07111 
Customers upgrading from 7.2.x may notice errors similar to the
following during 
cloning operations: 
38758 11/27/08 16:21:45 2 0 0 1 23334 0 <hostname> nsrd media 
warning: /dev/rmt/0cbn writing: posix async write: Error 0 
42506 11/27/08 16:21:45 2 0 0 1 23334 0 <hostname> nsrd media 
notice: LTO Ultrium-4 tape 64U00S00 on /dev/rmt/0cbn is full 
42506 11/27/08 16:21:45 2 0 0 1 23334 0 <hostname> nsrd media 
notice: LTO Ultrium-4 tape 64U00S00 used 89 MB of 800 GB capacity 
Workaround 
These issues may be related to a Solaris operating system limitation. If
you 
experience these errors, disabling asynchronous I/O capability may
resolve the 
problem. 
To disable async I/O capability: 
1. Shut down NetWorker 
2. Set the DISABLE_SOL_ASYNC_IO environment variable in the NetWorker 
startup script. The default location of the startup script is 
/etc/init.d/networker. 
3. Re-start NetWorker using the NetWorker startup script 
Note: With Async I/O disabled, performance impacts may be noticed during
cloning 
operations. 

Slow performance on Solaris 10 because asynchronous I/O is disabled 
LGTsc24548 
Due to a Solaris 10 operating system issue, asynchronous tape
input/output 
operations are disabled by default. As a result, some I/O intensive
operations such 
as cloning will be slower.   



----- Original Message ----
From: Joel Fisher <jfisher AT WFUBMC DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Monday, October 12, 2009 8:11:42 PM
Subject: [Networker] Sun Hardware

Hey Guys,



Can anyone give me an idea of how many lto-4 drives a T2000 or T5220
could keep streaming.



Assumptions.

Data is landed on disk(adv_file) then cloned to LTO-4 drives during the
day.

The disk is not a bottle neck.

Plenty of hbas so connectivity is not a bottleneck



Could I have say 3 landing areas and then stream to 3 LTO-4
simultaneously.  Somewhere between 120-240MB/s?



Any real world users of something like this.



I know these servers can seriously move some data, I guess my main
concern, is can they move a single stream fast enough for LTO-4 or
LTO-5?  Since any individual thread is limited to the 1.2-1.6Mhz.



Any advice here would be appreciated.



Thanks!



Joel 


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

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