NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/os/vms/19873

Internet Message Format | 1992-12-25 | 3.0 KB

Path: sparky!uunet!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
From: [e-mail] (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Writeback Cache and other trivia
Date: 25 Dec 1992 06:32:01 GMT
Organization: HST Wide Field/Planetary Camera
Lines: 50
Distribution: world
Message-ID: <[e-mail]>
References: <[e-mail]>,<[e-mail]>,<[e-mail]>
Reply-To: [e-mail]
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <[e-mail]>, [e-mail] (Harvey Brydon [phone]) writes:
=In article <[e-mail]>, in an incredibly polite manner,
=[e-mail] (Carl J Lydick) writes:
=>In article <[e-mail]>,
=>[e-mail] (Jerry Weiss) writes:
=>=During a regular test of my backup procedures (ie: my system crashed and
=>=when it came back up a few things didn't work ;-( )
=>
=>[generally good stuff deleted...]
=>
=>=Any there other files in VMS (not counting 3rd party software) that
=>=require special attention?
=>
=>For vanilla VMS, at least through v5.4-2, JBCSYSQUE.DAT is the only special
=>file, if you're concerned mostly about rebooting and having everything work
=>right.  If your real security-conscious, there are a couple of other files
=>(OPERATOR.LOG, and at least one AUDIT file) that you've got to worry about.
=
=You left out the ACCOUNTNG.DAT files.  These are never backed up to
=incremental backups because they are typically opened at boot time and never
=closed.  Since they are continuously open, you can't do the usual stuff with
=the file header (anything with "SET FILE", "SET PROT", etc.)  but you can mark
=them as modified by renaming them to themselves.  Give this a try.  It is
=directly from the incremental backup command procedure I use:
=
=$ set proc /priv=(sysprv,bypass)
=$ rename /log sys$sysdevice:[sys*.sysmgr]accountng.dat; *.*;*
=$ if f$search("sys$system:jbcsysque.dat") .nes. "" then -
=  rename /log sys$system:jbcsysque.dat;* *.*;*
=$
=$ backup /ignore=interlock ...

Mea culpa.  I'd forgotten about OPERATOR.LOG.  But if you REALLY want to
include that file, and don't want to use /IGNORE=INTERLOCK, then:
    $ SET PROC/PRIV=OPER
    $ DEF SYS$COMMAND _OPA0:
    $ REP/ENA
    $ REP/LOG
    $ DEAS SYS$COMMAND
    $ BACKUP ....
is a better idea.  If you don't want OPCOM messages to appear on the console,
then do a REPLY/DISABLE after the REP/LOG.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: [e-mail] | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.