> The PROBLEM with the ADSM implementation is that the client first
> sends (almost) 50 MB of the file to the server, before the server
> discovers that it doesn't really want to backup the file.
> This is really hurting our backups, because the files excluded
> by size are in excess of 100GB, and the ADSM backup process spends
> 99% of its time needlessly sending files across the network.
>
> QUESTION:  Can't the ADSM server/client protocol exchange the
> MAXSIZE=50m parameter once and for all, so that the client will
> never send the large files across the network in the first place ?
> Is there a way to configure such a behavior with ADSM ?

Do the huge files follow some sort of consistent naming convention? If so, you
might be able to attack the problem from a different direction by setting up
an include/exclude file with exclude statements for the huge files.