On May 26, 2010, at 11:20 AM, Rick Adamson wrote:

> We have an operations and security team that is constantly either moving
> client data or changing a file spaces inheritable ACL's, which in turn
> results in the next backup recognizing this as "changed" or "new" data
> and backing it up again. This results in wasted storage and reduces the
> retention history. 
> ...

Rick - My take:

Altering data path identities and attributes is something that a security group 
itself should be cognizant is bad practice.  Further, if you have auditors 
annually reviewing what's going on, they should be perturbed by this and stress 
to management that it should be curtailed.  I would file cost reports to 
management each time this is encountered so that there is full awareness, with 
the prospect of that resulting in curtailment.

Your only alternative may be backup based upon simple date, rather than 
comparing against a full list of Active files in the filespace.  But that type 
of backup has its own issues, of repeatedly backing up directories and missing 
files created after the "pointer" passed that area in the previous backup.

    Richard Sims     http://people.bu.edu/rbs/