This is one of the absolute stupidities one comes across in ADSM, due to
the fact that it doesn't really understand about Unix filesystems and
mountpoints.

I think you were _really_ asking why ADSM doesn't restore the /proc
_directory_, not the "filesystem".  The answer is that it doesn't back up
mountpoints for "filesystems" that aren't backed up.  Means you have to
manually create /proc, /tmp (I think) and any mountpoints for filesystems
that you aren't backing up.

Although this is a minor annoyance, it is one of the things that ensures
that I wouldn't recommend ADSM to anyone who just wants to backup Unix
systems to Unix systems, and for those that want to backup Unix systems to
mainframe tape libraries (as is the case with ours), I'd probably recommend
looking at the alternatives (another site I previously worked at used
harbor.)

michael

--------
Michael Lightfoot
Michael Lightfoot
Unix Consultant
Unix and Internet Team
Centrelink
Australia





"Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL> on 28/05/99 10:08:09 pm

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Michael Lightfoot/NSO/CSDA)
Subject:  Re: Solaris client




Note: Some recipients have been dropped due to syntax errors.
SMTP Headers are unavailable for viewing due to server configuration.



Hi Richard!
I know it's not worth restoring, but Solaris does require it to be present.
The user can add a line to his recovery scenario which instruct the user to
create this filespace manually after restoring, but I would like to know if
the exclusion of /PROC is hard-coded in the ADSM backup client.
Thanks for your reply!
Kindest regards,
Eric van Loon