Be aware that the "filesystem" is not equal to "all directories and files under the mount point tree"! So continuing with your example and assuming we have filesystems /work, /work/data and /work/data/martine: a file /work/dummy_file will give us FILESPACE_NAME='/work', HL_NAME='/', LL_NAME='dummy_file' /work/tmp/~12345 --> FILESPACE_NAME='/work', HL_NAME='/tmp', LL_NAME='~12345' /work/data/~12345 --> FILESPACE_NAME='/work/data', HL_NAME='/', LL_NAME='~12345' /work/data/garbage/empty --> FILESPACE_NAME='/work/data', HL_NAME='/garbage', LL_NAME='empty' .., etc. Under *NORMAL* circumstances /work filesystem DOES NOT have files under /work/data directory. Same for files under /work/data/martine in /work/data filesystem. But what if (just imagine, it is possible): - There are *really* three distinct file versions residing in three filesystems, i.e. three different files (!) with same path - the query points that this is archives of the file, not backups. And last two versions are made within five minutes (!) So my guess is that the user(s) have been working with this file tree for a long time, sometimes with one filesystem mounted, sometimes two or all three. As a result he/she(they) got (up to) three copies of the file(s). And whilst first archive can be assumed regular, most probably the last two were made with the intention to archive both - look at 5 minutes interval. This might happen if an application writes the file automatically (re)creating the missing path. And the filename (LL_NAME) also may lead to such conclusion.
Zlatko Krastev IT Consultant "Martin, Jon R." <[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 conventions /work /work/data /work/data/martine Would TSM back up each of these filesystems separately thus giving you three different file names? Thanks, Jon Martin -----Original Message----- From: Vo An 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 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: [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_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
