The reason we use snapdiff is to avoid walking the file system.  Running a 
periodic 'createnewbase' is just not going to happen.  We're just stuck with no 
time stamp.  - Margaret Clark

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Paul Zarnowski
Sent: Tuesday, February 14, 2012 4:08 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Need some support for snapdiff RFE's

Grant,

The time stamps are not updated, because a snapdiff incremental does not 
deactivate deleted files.  You need to do periodic 'createnewbase' to do this, 
which walks the file system and updates the time stamps.  

..Paul

On Feb 14, 2012, at 12:32 AM, "Grant Street" <grants AT AL.COM DOT AU> wrote:

> Hello
> 
> Just thought I would plug two snapdiff RFE's(Request For Enhancement) 
> that I created on the IBM developer works site.
> 
> I am trying to garner some support for these in the hope that they 
> will be implemented in the future.
> 
> I have seen that some of you have had experience with Netapp snapdiff 
> backups and you may have similar beliefs.
> 
> "Define snapdiff and other snap options on a per filesystem basis 
> rather than per backup command"
> When running an incremental backup be able to define the snapdiff or 
> other snap option on a per filesystem basis rather than for the whole 
> backup incremental job.
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=1
> 2858
> 
> "Snapdiff to update last backup fields in filespace data"
> Could you please update the TSM snapdiff client to update the 
> lastbackup information of filespaces when a "query filespace f=d" is 
> issued. This would be the obvious behaviour and would be inline with 
> the documented meaning of the columns
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=1
> 3145
> 
> TIA
> 
> Grant