As a workaround, you could create a management class/copy group that
specifies FREQUENCY 7, just for those files.

That would prevent them from being backed up more than once a week.
Reduce the pain a little.



On Thu, Jan 8, 2009 at 6:09 AM, Remco Post <r.post AT plcs DOT nl> wrote:

> On 8 jan 2009, at 11:34, Stephan Boldt wrote:
>
>  Hello everybody,
>>
>> we have an applications which changes the creation time (ctime) of
>> some big
>> files it uses, even though they are not really being recreated or
>> changed at
>> all. The modification time and filesize don't change, just the ctime!
>> Because of this changed ctime, TSM backs up these files every day
>> which is
>> really annoying, because they are rather big and their content hasn't
>> changed at all!
>> Is there a way to tell TSM to ignore the ctime?
>>
>>
> nope. On a real OS this would just be a file update (metadata only)
> but I guess your client is a windows system, so unfortunately, you're
> out of luck. Get the application fixed, updating the ctime on a file
> is bad behavior.
>
>
>  Thanks in advance!
>>
>> Kind regards,
>> Stephan
>>
>
> --
> Met vriendelijke groeten/Kind regards,
>
> Remco Post, PLCS
> +31624821622
>