Re: FILESPACE_NAME vs. HL

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." <jrmartin AT KNS DOT COM> on 03.01.2002 14:09:40
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
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