[Info-vax] Correct way to dismount shadowed volume set as late as possible?
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Thu Mar 25 20:32:14 EDT 2021
On 2021-03-26 00:13:20 +0000, Matthew Wilson said:
> But I can't just dismount DSA1 before running the @SYS:SYSTEM:SHUTDOWN
> command, because it obviously has data that's in use all the way
> through most of the shutdown process until the audit server is shut
> down.
> Hence my question -- what is the correct way to cleanly dismount such a
> shadow set that is needed all the way through audit server shutdown? Or
> is there an entirely different approach I should be looking at?
In general, add the DISMOUNT commands to SYSHUTDWN_0010.COM, or for a
later dismount during the SHUTDOWN.COM processing, add the DISMOUNT to
SYSHUTDWN.COM, as these are invoked automatically by SHUTDOWN.COM.
For this case, you're running a VAX version of OpenVMS VAX, and AFAIK
all versions that predates availability of SYSHUTDWN_0010.COM, so you
won't have access to that procedure here. The furthest back that the
MANAGE patch got was V7.3-2, IIRC. Which means you'll be dismounting in
SYSHUTDWN.COM.
You will want to quiesce the volume before the dismount, if there are
still open channels. (SHOW DEVICE /FILE ddcu: is one option to see
what's going on just before the DISMOUNT, etc.)
You will also want to use an edited version of
SYS$EXAMPLES:MSCPMOUNT.COM to mount and maintain volumes mounted—this
procedure can be configured and run and operates as a detached
process—and probably not what you're doing now with your MOUNT commands
in SYSECURITY.COM, as MSCPMOUNT contends with cluster member hosts
coming and going as can happen. I prefer to avoid using MOUNT /CLUSTER
here.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list