Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!necntc!ames!sdcsvax!ucbvax!noah.arc.CDN!kenw
From: kenw@noah.arc.CDN (Ken Wallewein)
Newsgroups: comp.os.vms
Subject: Error in MicroVMS Users Manual (p.1-23) ?
Message-ID: <885*kenw@noah.arc.cdn>
Date: Tue, 15-Sep-87 01:20:56 EDT
Article-I.D.: noah.885*kenw
Posted: Tue Sep 15 01:20:56 1987
Date-Received: Wed, 16-Sep-87 06:31:21 EDT
References: <1412@ogcvax.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29


  The manual is right. It's talking about a STAND-ALONE backup. This is done
in order to have NO files open during backup, to ensure complete accuracy.
You MUST have a Stand-alone Backup created  - or, in the case of Micro-Vaxen,
there's a special way to boot (can't remember the command right now, I can
check on Monday if you like). What happens it that the systems boots a very
abbreviated OS which has no memory management, process control, or anything.
All it can do is do backups. When you're done, you reboot the system again 
normally.
  You really only need to do this with your system disk. Any others you 
should be able to do with your users kicked off, or late at night, or whatever.
Backup will compain if if encounders open files. IGNORE=INTERLOCK will allow
you to back them up, but /VERIFY will complain if anything happens to them in
the mean time. Personally, I only do standalones once a month or so. Most of
the files that are open (see SHOW DEVICES/FILES) are not critical anyway.
But it's just possible to have something important get clobbered, so every
so often, we bring 'er down for a couple of hours or so...

  Hope this helps. Backup can be frustrating :-)


==================
/kenw
                                                                 A L B E R T A
Ken Wallewein                                                  R E S E A R C H
                                                                 C O U N C I L


-------