Are these by any chance NFS mounted directories? We do a lot of
archives with loopback-mounted filesystems, and over the course
of multiple iterations of the dsmc client we have found that
ADSM/TSM have treated these filesystems differently wrt to what
is FILESPACE_NAME and what is HL_NAME.
The proper way to find these files with a 'dsmc q arch' or
'dsmc retr' is to explicitly name the filespace in your filespec.
So, in your example, you have a single file which has been
archived under three different filespace names. Assuming you were
looking to retrieve the version of the file archived on
2001-12-22, you would issue the following command:
dsmc retr '{/WORK/DATA}/MARTINE/BS0266'
If you do not specify the filespace in your filespec, ADSM/TSM
will use the filespace that has the *longest* match, e.g., in
your case by default it will always find the version archived on
2001-11-20.
-- Tom
Thomas A. La Porte
DreamWorks SKG
[EMAIL PROTECTED]
On 01/02/2002 Mike Crawford wrote:
>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
>
>
