  Risks of BACKUP with /IGNORE=INTERLOCK? 
 The Question is:
 
Please can you tell me if there is any difference in a image backup done in
standalone mode (Stabackit produced) and a image backup done with a "min"
boot using the "/ign=inter"
parameter ?
 
Thanks
 
 
 The Answer is:
 
  BACKUP /IGNORE=INTERLOCK is equivalent to the (entirely hypothetical)
  BACKUP qualifier /ALLOW=DATA_INCONSISTENCIES.
 
  The use of BACKUP /IGNORE=INTERLOCK should be interpreted to indicate
  that data inconsistencies are expressly permitted by the caller -- the
  interlocks being overridden are implemented for a reason, and ignoring
  them indicates an acceptance on the part of the caller of potential
  corruption problems.
 
  Experienced OpenVMS system managers can usually restore on-line
  BACKUP/IMAGE savesets, though it is likely that some file data
  inconsistencies can arise among the open files, and also also possible
  that some information and configuration data will need to be manually
  recreated.  Particularly experienced system managers -- those familiar
  with the OpenVMS system disk structure -- can also often restore a
  BACKUP non-/IMAGE saveset to disk, though this restoration cannot be
  performed solely using the OpenVMS VAX standalone BACKUP environment
  and -- like the use of /IGNORE=INTERLOCK savesets -- can involve some
  inconsistencies and loss of data among open files.  (The steps involved
  either of these two restorations are generally site-specific, can and
  often do vary by the particular inconsistencies encountered, and are
  not particularly documented.)
 
  For an entirely consistent BACKUP (and one that can be restored without
  particular knowlege of the OpenVMS system disk structure and without
  having to recreate certain parts of the local system configuration),
  the OpenVMS Wizard recommends that the target disk be quiescent -- all
  applications shut down.  In the case of an OpenVMS system disk, acheiving
  quiescense is possible only through the use of standalone BACKUP (OpenVMS
  VAX) or the bootable CD-ROM environment (OpenVMS Alpha) or OpenVMS running
  on another disk (with OpenVMS on the source disk shut down).
 
  Information on BACKUP /IGNORE=INTERLOCK as well as information on
  performing a system disk BACKUP is included in the OpenVMS documentation
  set, available via http://www.openvms.digital.com:8000/
 
