ADSM-L

Re: Wildcards and Restores

1995-09-27 16:55:50
Subject: Re: Wildcards and Restores
From: Andy Raibeck <raibeck AT CONNIX DOT COM>
Date: Wed, 27 Sep 1995 16:55:50 -0400
As far as filtering goes, the "*" means zero or more characters - ANY
characters, including the "." in the file names. You should be able to
restore a single drive with one command, i.e.

     RESTORE -SUBDIR=YES -REPLACE=NO -TAPEPROMPT=NO C:\*

Yes, wildcards are handled a little differently between ADSM commands
and the INCLUDE/EXCLUDE list. With ADSM commands, there is not quite the
same flexibility. I don't think there's a way to specify more than one
drive at any time. The only reason I can think of for this is that ADSM
stores data in a structure called a "filespace". The high-level name of
the filespace is the drive label, not the letter. ADSM does no internal
association of labels to letters. For example, suppose you have the
following drives and labels:

C: = IBMDOS_6
D: = OS/2
E: = DATA

ADSM stores the data in filespaces with high-level names of "IBMDOS_6",
"OS/2", and "DATA". It knows nothing of the "C:", "D:", or "E:".

If you had a new drive labeled "DRIVE-C", the following command would
not work:

     RESTORE -SUBDIR=YES -REPLACE=NO -TAPEPROMPT=NO C:\*

ADSM would look for a filespace with a high-level name of "DRIVE-C",
but wouldn't find anything. Thus it would report back no backup versions
found.

Instead, you'd have to do this:

     RESTORE -SUBDIR=YES -REPLACE=NO -TAPEPROMPT=NO {IBMDOS_6}\* C:\

This would then restore the data to the C: drive.

What I'm getting at is that for multiple filespaces, ADSM would not
know which filespaces go where (unless perhaps the drives were
labeled to match filespace names). This is something maybe IBM should
consider implementing. Maybe they could add syntax to specify the
filespace names for source file spec and drive letters for the target
file spec, where there would be a one-to-one relationship between
the nth filespace name and the nth drive letter.

Hope this helps,

Andy Raibeck
Connecticut Mutual
203-987-3521

-------- Forwarded letter follows --------
I thought I knew how this worked, but it seemed to behave differently
I thought I knew how this worked, but it seemed to behave differently
yesterday.  Perhaps someone (IBM?) can correct my misunderstanding.

When we had IBM to teach the ADSM class (in March of '94; for release 1),
the
instructor talked about the difference between datasets with suffixes (in
a
DOS or OS/2 environment) vs. those that did not.  His recommendation at
the
time was to handle them separately - use both *.* and * as distinct
entities.

Yesterday I had to restore a full hard drive (actually 3 logical drives)
using
ADSM and the OS/2 command line interface.  for the FAT drives, I entered
the
following:

   Restore e:\*.* -subdir=yes -replace=no -tapep=no

The result was a restore of what appeared to be all of my drive.  A second
pass, using the following was made:

  Restore e:\* -subdir=yes -replace=no -tapep=no

The result was no new files, but I did gain 2 subdirectories!  I also
spent a
lot of time doing it, as I had to pass 3 volumes of tape for the restore.

I did the same for the D drive with the same response.  One answer was
that
there were no data sets without suffixes, but I don't *believe* that to be
the
case.  BTW, I restored the C drive (which is HPFS, not FAT) with one pass,
with the following command:

  Restore c:\*.* -replace-no -tapep=no

All subdirectories were restored, even though I didn't tell it to follow
the
chains.  OS/2 resides on the C drive.

Is it still necessary to make the two passes, or has there been a change
in
processing.  I would prefer a single pass - the multiple passes with
multiple
tapes is a real pain.

Also, I noted an inconsistencey in the way wildcards are handled between
exclude/include processing, and the restore commands.   On page 70 (top)
of
the version 2 OS/2 client manual (SH26-4053), it shows using multiple
letters
for the drive - [ce-g] to indicate drives c, e, f, and g.  This does not
work
on a restore command - it comes back and tells me that there were no files
backed up for this combination.  Shouldn't the syntax for wildcards be
followed throughout?  If this was valid, I could make one pass of my
restore
tapes, instead of three!  Otherwise it should say the syntax is incorrect,
not
that I didn't back anything up.

signed - wishing in Hartford
Jerry Lawson
<Prev in Thread] Current Thread [Next in Thread>