Hello Mike,

In UNIX, a filespace for ADSM is a filesystem. So in this case,
it looks like the /work is the filespace unless you have mapped
a directory like /work/data as a nfs at the time of the backup or
perhaps you have used the client option virtualmountpoint.
Hope this helps.

Regards,

Vo An Nguyen
Email: vanguyen AT ca.ibm DOT com



Mike Crawford <mcrawfrd AT telusplanet DOT net>@VM.MARIST.EDU> on 01/02/2002
04:11:23 PM

Please respond to mcrawfrd AT telusplanet DOT net

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  FILESPACE_NAME vs. HL_NAME


Good Afternoon,

A client is having trouble locating archived files using dsmc q ar.  The
problem
seems to be that the filespace_name and hl_names differ between the files,
even
though they were archived from the same place.

Server: AIX, ADSM v3.1
Client: SunOS, ADSM v3.1

An example:
select filespace_name,hl_name,ll_name,archive_date from archives where
node_name='HUBER'
and ll_name='BS0266'


FILESPACE_NAME: /WORK
       HL_NAME: /DATA/MARTINE/
       LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:46:30.000000

FILESPACE_NAME: /WORK/DATA
       HL_NAME: /MARTINE/
       LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:41:24.000000

FILESPACE_NAME: /WORK/DATA/MARTINE
       HL_NAME: /
       LL_NAME: BS0266
  ARCHIVE_DATE: 2001-11-20 05:38:10.000000


Depending on how the client specifies the request, they will get a
different
version of the file.

The question is, how does ADSM determine which part of the path is
considered
filespace_name, and which is hl_name?

Thanks,
Mike