Fazil Saiyed wrote:
> Also remember that certain condition must exist for this behavior to 
> occur.
> i.e client is slow to backup , networker parallelism is high or higher.
> Tape speed is faster then data coming into networker server, therefore it 
> will save to memory until it's full then write it in 2 GB increment, this 
> type of implementation would get around show shining of  tape drives.

This is not true at all. It's nothing to do with performance or
shoe-shining. This behaviour is limited to older unsupported versions of
NetWorker or older unsupported versions of application modules. The
possible exception is NetWorker for Netware which has always lagged
behind NetWorker on other platforms.

The other possible case would be special debugging builds of NetWorker.
It has been known in the past for special versions of NetWorker provided
by EMC Engineering to exhibit this behaviour.

The proper terminology for this is "continuation save sets".

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