Path: utzoo!attcan!uunet!husc6!think!ames!pasteur!ucbvax!ISUMVS.BITNET!GG.SPY
From: GG.SPY@ISUMVS.BITNET ("John Hascall")
Newsgroups: comp.os.vms
Subject: Re: Backing up the system disk from DCL
Message-ID: <8808081535.AA09548@ucbvax.berkeley.edu>
Date: 8 Aug 88 14:09:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 36

> Date:         Wed, 3 Aug 88 11:54:54 EDT
> From:         "M. Abbonizio" <abbonizi@NADC.ARPA>
> Subject:      Backing up the system disk from DCL
> To:           John Hascall <GA.JPH@ISUMVS>
>
> Hello VMS managers,
>
>    Does anyone backup their system disk from the DCL command level?  What are
>    the drawbacks?  Do you use /IGNORE = (INTERLOCK or NOBACKUP)?  What effects
>    does this have on PAGEFILE.SYS and SWAPFILE.SYS which are marked "No Backup
"
>    when restored?  Any info or hints appreciated.
>
>    The system is a cluster running VAX/VMS 4.5.
>
>       Mike Abbonizio
>

   I use:

      $ backup /buffers=5 /ignore=interlock /image /record /rewind -
         'disk'  'save_set'/LABEL='backup$volser'

   (Note that this is in a command procedure, hence the symbols...)
    It just gives a message that the files are marked NOBACKUP and
   continues on it's merry way.

     While on the subject of backup  (* FLAME ON *)  One thing which
  annoys me to no end is that when you specify /record (to record the
  time of the backup in the file header) and a user deletes a file after
  the time it is backed up and the time the file header is to be updated
  backup gets all bent out of shape...It would certainly be nice if this
  was handled as nicely as /nobackup files are..

John Hascall
ISU Comp Center