I search of the file system will not start a recall. At one time some 
anti-virus programs could cause recalls but that has long since been fixed. 
Still, if you have a rare 3rd part AV provider you'd want to test.
   
  With mos HSM you only ever have a single copy of the HSM file. So when a new 
file is created on the real system the copy in HSM is expired.  Then after that 
new copy meets your HSM requirements it will be sent to the backend HSM 
storage.  Remember HSM is the origional file and is not a backup version.
   
  When the source stub file is delete the default should be to remove the file 
from the HSM storage. That may not happen until the next time the HSM scan of 
the file system is done.
   
  I really don't have specific information on the new Tivoli HSM product. This 
is all from my knowlege of DiskXtender.

Volker Maibaum <volker.maibaum AT EBERSPAECHER DOT COM> wrote:
  Hello,

we are also thinking about the possibility of using HSM on our Windows
Fileservers.

I was wondering what happens if a user is opening the search dialog of
the windows explorer and searches for all files on a filespaces
containing the string "XYZ".
Would this start a retrieve of all files previously migrated to TSM? If
so, could this be avoided in some way?

Is there way how to delete all previous versions of a file in
HSM-archive when a new version is migrated?

What happens with files in HSM-archive when a user deletes a stub-file
(because he doesn't need the file anymore)? Is the archived file also
deleted? Or does the archived data grow on forever?

regards,

Volker
  


                
---------------------------------
 Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more on new 
and used cars.