The difference between the "Inspected" and "Backed up" number most likely lies
in your exclude list.  There are files there that will not be included in a
backup - things like swap files in a Windows or OS/2 system.  IN a NetWare
system, they include things like print queues and NetWare forward recovery
data sets.

I am not sure about the difference on the restore, assuming that this was a 1
to 1 backup to restore example.  The only thing I can think of is either a
data set that is marked as "Read Only", and you didn't tell ADSM to restore re
ad onlys, or perhaps a boot file that was backed up but is now back on the
hard drive, and you said "do not replace' as an option.

BTW, I would be curious to know the results of your test.   I would expect
that the questions you raised about files are client related, not server, and
so should be the same for both tests.

Jerry Lawson
jlawson AT itthartford DOT com

________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Missing files on restore
04-04-96 12:32 PM

Hi folks!

I'm running some performance tests with ADSM backing up a NetWare 3.12 server
to both MVS and AIX to see which platform provides the best throughput.
I backed up a directory which contained 5,537 files and consumed exactly
377,031,144 bytes (I got this from the DOS dir /s command).

When I ran the backup to MVS the ending statistics were:
  files inspected: 5537
  files backed up: 5531
  failures: 0

My first question is why were 6 files not backed up?  Were these 0 length
files?  What else causes ADSM to not backup a file?

I then deleted the entire directory tree and ran a restore.  Another dir /s
command shows only 5,530 files, but still consuming 377,031,144 bytes.  My
second question is what happened to 1 file?

Has anyone else encountered this?  I'm sure there's a good reason, I just
don't know what it is.  Any explanations are sure welcome.

Thanx!

Jeff Renicker
jrenicker AT vnet.ibm DOT com