File data is compressed on-the-fly, as the data is read off the client disk
and sent to the server. There is no buffering of the entire file (in memory
or disk) in order to first compress it before sending it to the server.
Likewise, with restore, the data is decompressed as it is sent from the
server and written back to client disk.

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/25/2006
07:49:10 AM:

> Our aix admin had a question about client compression that I couldn't
> find an answer to in the docs.  He was wondering where the compression
> actually takes place on the client end.  Does the compressed file get
> written to disk as it's being created, then deleted after it's sent?  Or
> does the compressed version of the file get created in memory
> temporarily until it's sent?  Or is it happening some other way that
> didn't occur to me.
>
>
> Confidentiality Notice follows:
>
> The information in this message (and the documents attached to it, if
any)
> is confidential and may be legally privileged. It is intended solely for
> the addressee. Access to this message by anyone else is unauthorized. If
> you are not the intended recipient, any disclosure, copying, distribution
> or any action taken, or omitted to be taken in reliance on it is
> prohibited and may be unlawful. If you have received this message in
> error, please delete all electronic copies of this message (and the
> documents attached to it, if any), destroy any hard copies you may have
> created and notify me immediately by replying to this email. Thank you.