Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ecsvax.UUCP!mxc
From: mxc@ecsvax.UUCP.UUCP
Newsgroups: mod.computers.vax
Subject: Submission for mod-computers-vax
Message-ID: <8704021523.AA00510@ecsvax>
Date: Thu, 2-Apr-87 10:23:15 EST
Article-I.D.: ecsvax.8704021523.AA00510
Posted: Thu Apr  2 10:23:15 1987
Date-Received: Sat, 4-Apr-87 17:16:15 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Path: ecsvax!mxc
From: mxc@ecsvax.UUCP (Mark Cooperstein)
Newsgroups: mod.computers.vax
Subject: VMS Backup question
Message-ID: <2852@ecsvax.UUCP>
Date: 2 Apr 87 15:23:14 GMT
Organization: UNC Educational Computing Service
Lines: 18
Keywords: VMS BACKUP UTILITY

I have read somewhere that using the /NOCRC switch whilst doing
vms backup will significantly decrease the backup time by allowing
the hardware controllers themselves to take care of this function.
In particular, the use of software CRC checking (the default in
the backup utility) has large overhead on microvax II due to the
fact that it uses some instructions that are emulated in microcode.

My question is this:  We have an SI/Fujitsu Eagle drive.  The only
backup medium I have is the TK50 drive.  If I use the /NOCRC switch,
will the TK50 controller be able to handle potential write errors if
they ocurred?  Should I avoid this or not??

Thanks,

Mark Cooperstein
NCSU School of Vet. Medicine
Raleigh NC