But now that I think about it, if you're backing up this way, there really is 
NO value in using client compression (the directives with compression), (there 
hardly ever is).  

You're not saving any bandwidth, as all the data will still come across the 
network.  You're then compressing it with software in NetWorker.  This takes 
longer and won't be as efficient than just using the tape drive compression.

Why would you want to do it this way?


Curtis Preston  |  VP Data Protection  
GlassHouse Technologies, Inc.
 
T: +1 760 710 2004 |  C: +1 760 419 5838 |  F: F: +1 760 710 2009  
cpreston AT glasshouse DOT com |  www.glasshouse.com
Infrastructure :: Optimized

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of kurianv
Sent: Monday, August 25, 2008 2:58 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] enabling compression

hi,
thanx for the valuable suggestions...but davina how can we force the tape 
drives not to compress if we are using "NT with compressed directives".

thnx, 
kurian



davina wrote:
> kurianv wrote:
> 
> > hi,
> > sorry i did not tell in detail...actually we are using sdlt tape drives of 
> > 320 GB capacity
> > And whereas in the case of netapp filer..what we have done is that now we 
> > have mapped the drives of filer in a windows server. So now the client is 
> > windows server. And when the backup is taken the maapped drives of the 
> > filers are also backed up....
> > 
> > Please can u suggest on the way how we can enable compression in this 
> > case..?
> > 
> 
> The best compression will come by using the compression of the SDLT 
> drives. If you insist on using software compression you do this by 
> selecting "NT with compression directives" in the client resource. If 
> you do this I suggest that you force the tape drives NOT to compress, as 
> double compressing negates the effect and sometimes ends up backing up 
> more data than just using hardware or software compression.
> 
> Software compression is (IMHO) best reserved for those cases where the 
> client is connected to the storage node via a very slow network connection.
> 
> 
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


+----------------------------------------------------------------------
|This was sent by kurianji AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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 email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this 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