John
Whats hapeening is ADSM is backing up your files using a DOS 8.3 filename
instead of the long filename. This is the way ADSM works, as far as I know. It
does not back up files using the long filename. I believe if you restore the
file the long filename will be restored but the problem is you can not use the
long filename to choose which file to restore. I think what
ADSM or Novell does is truncate long filenames to 8 characters and checks to see
if a file with that name exists. If a file with that name does not exist ADSM
uses that name to backup the file. If a file with that name does exist, the
last character(s) is replaced with the next sequential number which would make
the filename unique and that 8 character name is used to back up the file. For
example:
long file name longfilen1 would have a DOS name longfile
long file name longfilen2 would have a DOS name longfil0
long file name longfilex2 would have a DOS name longfil1
long file name longfilee4 would have a DOS name longfil2
long file name longfilee5 would have a DOS name longfil3
long file name longfilex6 would have a DOS name longfil4
long file name longfile12 would have a DOS name longfil5
long file name longfile80 would have a DOS name longfil6
long file name longfilecd would have a DOS name longfil7
long file name longfileff would have a DOS name longfil8
long file name longfilezz would have a DOS name longfil9
long file name longfileaa would have a DOS name longfi10
As long as the first e characters of the file name are the same this is how it
works.
John Schneider <jdschn AT ibm DOT net> on 05/11/99 05:56:29 PM
Please respond to jdschn AT ibm DOT net
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Ronald Heflin/Chicago/IBM)
Subject: Novell client missing long files in backup
Greetings,
We are running the Novell 3.1.03 client backing up to a 3.1.2.20
server under Solaris
2.6. Three times we have had a problem restoring files on the Novell
clients. It looks as if
the file has not been backed up to begin with. With the Novell restore
client we can see
other files in the same directory where the file ought to be. We are
using -pick and -inactive
so I know we ought to be seeing the files if they were originally backed
up. The last time
that happened, we went looking back at the dsmsched.log several days we
know the file
was there, and was being changed, and should have been backed up, but
the file is not
in the dsmsched.log, even though other files in that same directory are
being backed up.
There is nothing in the dsm.opt to exclude the file.
Here is the interesting part. In each of these cases, the missing
file has a long file name,
and there is another file in the same directory that has the same name
for at least the first
8 characters! Is it possible that the Novell client is overlooking the
file, and not backing
it up because there is another similar looking file in the directory?
It kinda looks that way.
I know the .06 Novell client is out, we will install that and see if
it helps, but if you
have heard of this, please let me know.
Thanks in advance,
John Schneider
***********************************************************************
* John D. Schneider Email: jdschn AT ibm DOT net * Phone: 314-349-4556
* Lowery Systems, Inc.
* 1329 Horan Disclaimer: Opinions expressed here are
* Fenton, MO 63026 mine and mine alone.
***********************************************************************
|
