Yes Mattice. A "dsmc q backup /test/*" will only show files. You
must use "dsmc q backup /test/* -dirsonly" to see directories.

Frank

Mattice Dave wrote:
>
> I have tried this procedure and but, did not get it to work.  We are
> using
> ADSM Server version 2.1.9 for AIX and Client version 2.1.6 for HP-UX.
>
> A directory called "/test" was created with one file and one empty
> sub-directory then a "dsmc selective -subdir=yes /test" was done.
> A "dsmc q backup /test/*" showed only the file, the empty sub-directory
> was not displayed.  A file was created in the empty sub-directory using
> "touch /test/empty-dir/file" and then the file was removed to update the
> sub-directory time stamp.  Next a "dsmc incremental -subdir=yes /test"
> was done.  A "dsmc q backup /test/*" showed only the file, the empty
> sub-directory was not displayed.
>
> Can someone tell me if I have missed something.
>
> Thanks
> Dave Mattice
> MCI Systemhouse
> dmattice AT shl DOT com
>
> >Hello LAbbinante,
>
> >I've seen this complaint before, and we are changing ADSM so that
> >empty directories are backed up with the selective backup command.

> >You see, ADSM currently does backup empty directories, but ONLY if
> >backups are done using the incremental command. But, for various
> >reasons, all our users don't use the incremental command, some
> >use only the selective backup. Thus, the directory entries are never
> >backed up to start with.
>
> >Restore does currently restore empty directories, but it only does so
> >if the subdirectory option is used. The one caveat here is that you
> >currently can not restore only the empty subdirectory. It must be
> >contained within another directory that actually has files in it.
> >This too will be fixed with version 3.
>
> >Until the new function is available, via Version 3, I suggest that
> >you look into using the incremental command for backup.
>
> >LAbbinante wrote:
> >>
> >> I know this has been an old standing question/problem with ADSM
> >> restores.  However,  we recently had a restore of a 60% full 4GB
> >> filesystem that had 366,000 files in it, and the issue, even though it
> >> was KNOWN to be a limitation, has come up again.   The file system in
> >> question was corrupted, and HP, knowing that ADSM was our
> >> backup/recovery tool, said to reinitialize the filesystem and restore
> >> from scratch.  After the restore kicked off( which ran at about 28,000
>
> >> files/hr.  366,000/28,000=13+hrs), it was brought to my attention that
> >> files were being missed.  Not files, I found out, but
> >> directories,....empty directories.   It was decided about three hours
> >> into the restore to cancel it and recover a fresh unloaded
> >> (directories/no data) filesystem from other servers.  Needless to say,
> >> ADSM has been put on the spot for not only for its performance (which
> >> is due to it's 10mbit connection to MVS), but for the existing problem
> >> of not restoring empty directories.   Does anyone have an update or
> >> workaround, on this old, seemingly persistent problem. :-(
> >> Thanks,,,Larry