Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!MITRE.ARPA!sherr From: sherr@MITRE.ARPA (Guy Sherr) Newsgroups: comp.os.vms Subject: Re: VMS 4.6 and Backup Message-ID: <8710072101.AA03513@mitre.arpa> Date: Wed, 7-Oct-87 17:01:09 EDT Article-I.D.: mitre.8710072101.AA03513 Posted: Wed Oct 7 17:01:09 1987 Date-Received: Sat, 10-Oct-87 17:45:30 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The MITRE Corp., Washington, D.C. Lines: 73 Replying-to your message received on Tue, 06 Oct 87 18: 13:00 -0700 Date: Wed, 07 Oct 87 17:01:01 EDT From: sherr [more bug] My experience with backup in 4.6 is as odd. I have a fairly large configuration which (until this AM) includes two vaxes running 4.6 and one running 4.3. The two running 4.6 are an 8700 and an 11/730. For the 8700, the tape drive is a tu81+, but for the 730 is a Kennedy with a dilog lookalike controller. The 8700 would not write a backup tape, with the same error message. Since the console is a vr201+pro/380, and since the command itself was issued (in no procedure), this may have been considerably different. The interesting thing about this is that I put the saveset on another disk (it was small, but an image), and copied it to the tape successfully with the copy command. 4.6 backup was able to READ the saveset, but could not append another to the logical end-of-tape; SAME error. The 730 works fine. Other than being somewhat slow, it was able to write an image backup tape (differing equipment may have made the difference). -- Guy Sherr, MITRE corp., McLean, VA. -- sherr@mitre.arpa Received: from wiscvm.wisc.edu by KL.SRI.COM with TCP; Tue 6 Oct 87 18:16:43-PDT Received: from YMIR.BITNET by wiscvm.wisc.edu ; Tue, 06 Oct 87 20:16:35 CDT Date: Tue, 6 Oct 87 18:13 PDT From: Chris Yoder Subject: VMS 4.6 and Backup To: info-vax@kl.sri.COM X-Vms-To: INFO-VAX-SUBMIT,CHRIS [bug food] Well, I took that giant leap of faith forward and installed VMS 4.6... So I'm wondering if anybody else has had the following problem, or if it's just a hardware problem: Hardware in question: 11/750 (we're on a tight budget...) and TU81+. (The 750 is the boot node of a LAVC that includes a uVAX II and a Vaxstation 2000.) Software in question: Backup or DCL. Problem: I have a command procedure that does the backups that I need to do when I need to do them. It backs up various disks to tapes mounted on the TU81+. When run as a batch job (usual case that worked fine under VMS 4.5C) the following BACKUP command generates the errors: $ backup/image/ignore=interlock/jour=BACKUP$JOURNAL:MONTH10_MATH2.BJL - MATH2: - MUA0:MATH2.bkp/block=32528/density=6250/label=D31006 - /norewind/buffer=5/nocrc/fast %BACKUP-F-LABELERR, error in tape label processing on _HELA$MUA0:[]MATH2.BKP; -SYSTEM-F-BADPARAM, bad parameter value When the *exact* same command procedure is run on the console terminal (a DECwriter III) with verify enabled it works just fine, and does *not* generate any such errors. Both processes are running at prio 4 and have the same privileges. I have attempted to place a wait statement prior to the backup command thinking that the tape drive needed a minute or two to synchronize, but that didn't help. Anybody have similar experiences? ideas? (Shooting that tape drive at dawn isn't an option :-) ) I am currently suspecting 4.6 backup, but I cannot be certain. -- Chris Yoder Internet --- Chris@Ymir.Claremont.Edu Harvey Mudd College Bitnet ----- Chris@Ymir.Bitnet