Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ucla-cs!zen!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: Error in MicroVMS Users Manual (p.1-23) ?
Message-ID: <870912035933.000@CitHex.Caltech.Edu>
Date: Sat, 12-Sep-87 07:06:48 EDT
Article-I.D.: CitHex.870912035933.000
Posted: Sat Sep 12 07:06:48 1987
Date-Received: Sun, 13-Sep-87 09:46:35 EDT
References: <1412@ogcvax.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 22


 > This question may sound stupid to most people reading this newsgroup,
 > since I am totally new both to the VMS system and as a system maintenance
 > personnel.
 > 
 > On page 1-23 of the MicroVMS User's Manual (Vol.1), there is a step by
 > step procedure describing how to perform a full system backup. The first
 > step reads as follows:
 > 
 >   1. If the system is running, shut it down as explained in Section 1.1.2.
 > 
 > Is that an error? My understanding (very limited) is that after the system
 > is shutdown, the control is transfered to the console monitor, which
 > dosen't (?) understand commands such as INITIALIZE, MOUNT or BACKUP.

You should have continued reading further.  The next step is to boot standalone
backup, which understands the BACKUP and ONLY the BACKUP command.  On the
other hand, you don't necessarily need a standalone backup.  Except in the
case that a file is open for update in such a way that it may be rendered
inconsistent (software that takes full advantage of RMS capabilities usually
doesn't have this problem; software ported from other operating systems
may), you can simply do a "BACKUP/IMAGE/IGNORE=INTERLOCK" instead.