Hm....interesting. I found out, that this behaviour only occurrs when the
delete file is still in the trashbin. Well that's great but I didn't expect
that! Does that mean you can move migrated files without restoring them?
Does that even work across different drives?

Kind regards,
Stephan

On Thu, Jun 4, 2009 at 1:16 PM, Stephan Boldt <
stephan.boldt+adsm-l AT gmail DOT com <stephan.boldt%2Badsm-l AT gmail DOT 
com>> wrote:

> Well, I didn't. NOW I did and 1 file has been deleted from the archive. But
> I was still able to search and restore the deleted file from the HSM client
> GUI!?! How the hack can that happen? Any Ideas? I'm totally confused... :-/
>
> kind regards,
> Stephan
>
> 2009/6/4 Bos, Karel <Karel.Bos AT atosorigin DOT com>
>
> Did you ran expire inventory?
>>
>> Regards,
>>
>> Karel
>>
>> ----
>>
>> Hello everybody,
>>
>> I'm trying to set up HSM (TSM 5.5.2)  for our Windows fileserver. For
>> testing purposes I've created a folder c:\temp\hsmtest and put a file
>> into that folder. I set up a hsm job for that folder and ran it whicht
>> worked as
>> expected: The file has been moved into the tsm archive and has been
>> replaced by a stub file. Retrieving the file also worked as expected.
>> Next (after migrating the file into the archive again) I deleted the
>> stubfile to test the reconsilliation (the archive copy groups "retain
>> version" value is set to "nolimit"). I ran the reconsilliation via the
>> HSM Client GUI, but after that the deleted file was still in the archive
>> (is still listed when looking for it via the search & retrieve command
>> in the GUI).
>>
>> Why is this so? What do I have to do to get rid of the deleted file in
>> the archive?
>>
>> Thanks in advance for you help!
>>
>> kind regards,
>> Stephan
>>
>>
>