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 p
t; <[EMAIL PROTECTED]> on 03.01.2002 14:09:40
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject:Re: FILESPACE_NAME vs. HL_NAME
Along thos same lines maybe if there are three file systems with the
following naming co
Nguyen/Quebec/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 02, 2002 5:01 PM
To: [EMAIL PROTECTED]
Subject: Re: FILESPACE_NAME vs. HL_NAME
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
An Nguyen
Email: [EMAIL PROTECTED]
Mike Crawford <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/02/2002
04:11:23 PM
Please respond to [EMAIL PROTECTED]
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: FILESPACE_NAME vs. HL_
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 file
