The API used on the filesystem side really shouldn't have any effect on
the backend implementation.

The reason it's different is because Tivoli/IBM purchased the product from
a separate company.

As such, HSM for Windows is not derived from HSM for AIX.


The Redbook doesn't clarify all of the info, but it does indicate NOLIMIT
is recommended.   The actual Tivoli whitebook clearly states many
limitations and exceptions.

The regular BA client will only back up the stub (NTFS junction) once
migrated, and if the stub's permissions change, it is rebacked up.

The BA client doesn't integrate with nor is it aware of the behaviour of
the HSM for Windows client.

Backup before Migrate shoudl also be used.  This will back up the file
via the HSM client.

HSM for Windows clients should have a separate policy domain.
There should be only the default management class.  The copygroup for
backup and archive should both be set to NOLIMIT.

In the future, there may be the ability to delete versions of migrated
files from the HSM GUI.



On Thu, 29 Mar 2007, Helder Garcia wrote:

Date: Thu, 29 Mar 2007 06:08:49 -0300
From: Helder Garcia <helder.garcia AT GMAIL DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: HSM for Windows

I think the majority of tools that implements truly hierarchical space
management must rely on DM API - http://en.wikipedia.org/wiki/DMAPI , which
is not supported by NTFS, that's why HSM for Windows is a "specific"
implementation, a really separate product from space management for Unix.

On 3/28/07, Weeks, Debbie <debbie AT admin.usf DOT edu> wrote:

Thanks.  We are HIGHLY disappointed with this product.  I have reviewed
the documentation again, and still do not find this little caveat
spelled out clearly anywhere in what we have.  I used to administer
IBM's SMS/HSM on MVS back in the day, so I guess my expectation were
high.  No wonder the license was so cheap!

Does anyone know if there are plans to make this a truly hierarchical
space management tool for Windows clients?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Remco Post
Sent: Wednesday, March 28, 2007 2:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: HSM for Windows

Weeks, Debbie wrote:
> I have not sent anything to this list in quite some time, so please be

> gentle if this topic has been thoroughly discussed in this forum
before.
> We are running TSM 5.3.4.0 on AIX, and recently purchased HSM to
> archive from our Windows  2003 file servers.
>
> In following the instructions to implement HSM we found that the
> documentation pointed to settings on the management class for HSM.
> However, once we implemented we found that those settings were not
> being recognized, and data was going directly to tape as indicated by
> the Archive settings.  We contacted support, and their response was
> that we needed to use the Archive settings to point our HSM jobs to a
> storage pool.  This doesn't seem right though, as we want files to
> initially go to disk, then migrate to tape according to a last access
> date, not based on a migration threshold on the storage pool.
>
> Does anyone out there have a hint as to why we cannot use the HSM
> settings?  Any help is much appreciated.

HSM for windows is designed to use the TSM archive API to store and
recall files. Therefore you must use an archive mgmtclass to manage
those files. Of course this can be a different mgmtclass than the one
used to manage your normal archive activities.

--
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten                      http://www.sara.nl
High Performance Computing  Tel. +31 20 592 3000    Fax. +31 20 668 3167
PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16  B3F6 048A 02BF DC93 94EC

"I really didn't foresee the Internet. But then, neither did the
computer industry. Not that that tells us very much of course - the
computer industry didn't even foresee that the century was going to
end." -- Douglas Adams

--
Helder Garcia