We are using Norton AV Enterprise 7.01 to scan our filer via CIFS. We have found that as Norton scans each file, the inode change time (i.e. ls -lc) gets set to the current time. I think it is due to Norton messing with the DOS archive bit, but I am not sure.
The problem is that this turns our level 1 ndmp dumps into virtual level 0 dumps. It seems that ndmp uses the inode change time, not the file modification time, as a basis for picking which files to dump during level 1's.
Any suggestions ?
Hi Paul --
You're encountering what we listed as burt 17767: RFE: Option to exclude files with ctime changed from filer incremental dumps, since Virus Checkers using CIFS often causes unwanted ctime changes.
On your filer console, just type : filer> ndmpd ignore_ctime ignore ctime comparison set to: true
(And if you want to toggle it off ...) filer> ndmpd ignore_ctime ignore ctime comparison set to: false
By doing this, the filer will only check for changed mtimes, not ctimes on incremental backups.
Burt 17767 is ONLINE, but the NDMP version of the workaround is not yet included in the burt description. But I just gave it to you, so there's no reason to worry.
Of course, you may want to look at the NOW site to make sure you have the right version of Ontap, etc...
Stephen Manley DAM And NDMP James Joyce groupie