ADSM-L

Re: Question about COMPRESSALWAYS

2015-10-04 18:11:36
Subject: Re: Question about COMPRESSALWAYS
The compressalways option is for API clients only.  The recent client
updates talk about supporting it, but the text is worded poorly.  What is
now supported is simply having the option be recognized and ignored by the
BA client, rather than have the BA client quit.

In an ADSM API program, the author must include code to send the file
uncompressed when compressalways=no and the file has grown during
compression.

The BA clients are designed this way.  If a file grows during compression,
the transaction is ended and rolled back.  Then all the files in the
transaction are sent uncompressed.

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.


_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Question about COMPRESSALWAYS
12-11-1996 11:48 AM

ADSM Win32 Client
Assuming in the Client Options file I have specified COMPRESSION ON:

The doc says that:

*       For COMPRESSALWAYS = YES, the object is sent even if it grows during
compression.

*       For COMPRESSALWAYS = NO, "Object is not sent if it grows during
compression."

Is this what really happens?

If the object is not sent at all during backup, that seems like a
serious exposure to me.
Users are not going to go through their DSMSCHED.LOG files to find all
the files that aren't sent because they expand.

What I want to happen when compression causes a file to grow is for ADSM
to retry sending it, uncompressed.  Is there a way to make this happen?

I
<Prev in Thread] Current Thread [Next in Thread>