Path: utzoo!attcan!uunet!husc6!cmcl2!nrl-cmf!ames!ucsd!nosc!humu!uhccux!helen
From: helen@uhccux.uhcc.hawaii.edu (Helen Rapozo)
Newsgroups: comp.os.vms
Subject: Re: VMS BACKUP hiccups
Summary: Might need priveleges or access to certain files.
Message-ID: <1943@uhccux.uhcc.hawaii.edu>
Date: 12 Jun 88 17:53:46 GMT
References: <8806112307.AA20396@ucbvax.Berkeley.EDU>
Reply-To: helen@uhccux.UUCP (Helen Rapozo)
Organization: University of Hawaii
Lines: 31

In article <8806112307.AA20396@ucbvax.Berkeley.EDU> KRAIG@BIOSTR.BIOSTR.WASHINGTON.EDU ("Kraig Eno, UW BioStructure") writes:
>Anyone know why BACKUP behaves this way?  I have a command procedure (shown
>below) which stops just after the first BACKUP command...no error or anything,
>it just doesn't execute the following commands.  If it's run batch, the job
>terminates at that point.  This is under 4.7, but it did the same thing under
>4.4.  I've tried various things, but it doesn't even seem terribly consistent.
>
>$ set verify
>$ set process/name="FULL Backup"
>$ allocate MUA0:
>$ initialize MUA0: FULL
>$ mount/foreign MUA0:
>$ backup/image/record/ignore=interlock DUA0: MUA0:SYSTEM.BCK
>$ ! This is where it halts.

What kind of error messages are you getting?

According to the VMS Manual (Version 4.4, page BACKUP-39), if you
use /IMAGE you will need write access to the INDEXF.SYS and BITMAP.SYS
for that volume.  Also if you have TU81+ tape drives you will also
need the PHY_IO privelege.

I also understand you will need OPER and READALL priveleges to
backup the entire drive.


-- 
BITNET address: helen@uhccux
UH Admin Network: HCCADA::CS_RAPOZO
US Mail Address: 874 Dillingham Blvd., Honolulu, HI 96817, Ph# (808) 845-9202
PLATO address: helen rapozo/honcc/hawaii