Interesting propsal, Mike: effectively a -preview mode for Backup. Note that, on Unix systems at least, an analogous function may be performed via the 'find' command, using a -mtime value relative to the last backup time for the filespace, which is granular to 24 hour time intervals. (Finer granularity could be had by using 'find' -mtime and -exec, to have a small Perl module do a stat() and test the file's last-modified time; or the more ambitious could write it all in Perl or C.) But it would take a dsmc facility as you propose to report the more interesting case of files now gone from the client which are still TSM space.
Richard Sims http://people.bu.edu/rbs
On Sep 17, 2004, at 8:04 AM, Mike wrote:
Since dsmc already knows how to read the local filesystem, how to parse the dsm.opt/dsm.sys/inclexcl.list, and how to talk with the tsm server, please (whomever) enhance dsmc with a switch such that when run on a local node, not with -virtualnodename, the program will load the dsm.opt, scan all local files, and scan the repository, then generate a list to stdout of all files on the local system that do not exist in the repository.
Mike