Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!nsc!voder!blia!ted
From: ted@blia.BLI.COM (Ted Marshall)
Newsgroups: comp.os.vms
Subject: SA Backup and page/swap files (was Re: AUTOGEN "feature")
Message-ID: <2818@blia.BLI.COM>
Date: Tue, 16-Jun-87 11:50:29 EDT
Article-I.D.: blia.2818
Posted: Tue Jun 16 11:50:29 1987
Date-Received: Sun, 21-Jun-87 07:38:36 EDT
References: <357bebf7.8be4@apollo.uucp>
Organization: Britton Lee, Los Gatos, CA
Lines: 26

In article <357bebf7.8be4@apollo.uucp>, jps@apollo.uucp (Jeffrey P. Snover) writes:
> ... When the system
> rebooted ("tried to reboot" that is) it choked saying
> something to the effect that the paging and swapping files
> were too fragmented to continue (boom). Wonderful...
> So I decided to do a stand alone backup and reorganize
> the disk.  (Boom)  It turns out that it too needs these
> files.  

Stand-Alone Backup includes a cut-down version of the VMS kernal. Thus, it
needs swap and paging files. Thus, if SAB is booted from a disk, it better
have valid swap and page files (as you discovered).

You can always boot SAB from the console medium. In cases where it is not
suitable for paging (i.e. TK-50 on a micro-VAX), the unsupported RAM disk
driver is included in the kit and so it swaps and pages to memory.

Note that this situation creates a nice little zapper: don't boot SAB from
a disk that you are then going to restore over. If SAB has to page, it'll
do it right over the restored data! (SAB may protect against restoring over
its "system" disk, I don't know off hand.)

-- 
Ted Marshall       ...!ucbvax!mtxinu!blia!ted <or> mtxinu!blia!ted@Berkeley.EDU
Britton Lee, Inc., 14600 Winchester Blvd, Los Gatos, Ca 95030     (408)378-7000
The opinions expressed above are those of the poster and not his employer.