This seems to be different then the way DiskXtender worked. I thought it had a 
process that reconsiled and cleaned up TSM.
   
  

"Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA> wrote:
  A field guide that has some information on the HSM for Windows:

http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=hsm+wi
ndows&uid=swg27002498&loc=en_US&cs=utf-8&lang=en

There is a section that contains differences from the unix hsm including
this:

TSM Server Reconciliation

Often, files are deleted in the user's file system after they have been
migrated to a TSM server.
Unlike TSM HSM for UNIX / Linux, TSM HSM for Windows requires an
administrator to query the
different versions of migrated files stored on the TSM server and to
manually delete those no
longer desired. Without this interaction, TSM server storage required
will tend to grow over time
even when the file systems managed are constant in size. TSM HSM for
UNIX / Linux schedules
periodic reconciliation processes to remove objects from the TSM server
when they no longer
map to files in HSM client file systems.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM_User
Sent: Friday, January 20, 2006 8:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] HSM on Windows Filesserver

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 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.
  


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com