ADSM-L

Re: [ADSM-L] HSM for Windows additional notice

2007-04-09 17:14:12
Subject: Re: [ADSM-L] HSM for Windows additional notice
From: Josh Davis <xaminmo AT OMNITECH DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 9 Apr 2007 16:13:41 -0500
One correction - recall on properties happens for executable file types.

Still need info on backup before migrate seeming to require HSM to use the
same node name as the baclient.

I'm at HSM 5.4.0.3 and TSMC 5.4.0.2


On Mon, 9 Apr 2007, Josh Davis wrote:

Date: Mon, 9 Apr 2007 15:56:43 -0500 (CDT)
From: Josh Davis <xaminmo AT omnitech DOT net>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: HSM for Windows additional notice

Notes about recall:
  Right click, properties
  If it's on a directory, it's ok.
  If it's on a migrated file, it forces a recall


Notes about DSMFILEINFO:
  dsmfileinfo doesn't seem to accept wildcards
  dsmfileinfo strips the backslash off of the end of quoted portions of the
filename



Something I have a question about:

If you have HSM back-up before migrate, it uses the BA client with a list of
files.

Once done, HSM logs in to see if the files were backed up. This means that
you cannot use a different node name for HSM without setting DSM_CONFIG.

Am I misunderstanding?  This seems to be a problem, since if you migrate,
you're guaranteeing you can only have one copy of the files.  The next backup
will back up the stub, and eventually, your real version will fall off the
other end.

This is all fine of the HSM config never gets damaged, and you use NOLIMIT
for the default archive copygroup, but that seems really limiting.


-Josh-Daniel S. Davis





<Prev in Thread] Current Thread [Next in Thread>