Xref: utzoo comp.sys.dec:584 comp.unix.questions:6104 comp.unix.wizards:7142 Path: utzoo!utgpu!water!watmath!grand!eclam From: eclam@grand.waterloo.edu (Edmund C. Lam) Newsgroups: comp.sys.dec,comp.unix.questions,comp.unix.wizards Subject: Re: Alternative backup devices for UNIX VaxStation 2000's Message-ID: <17602@watmath.waterloo.edu> Date: 17 Mar 88 13:44:53 GMT References: <1073@ndmath.UUCP> <4044@batcomputer.tn.cornell.edu> <538@hscfvax.harvard.edu> Sender: daemon@watmath.waterloo.edu Reply-To: eclam@grand.waterloo.edu (Edmund C. Lam) Organization: Shoshin Distributed Systems Group, University of Waterloo Lines: 24 In article <538@hscfvax.harvard.edu> pavlov@hscfvax.harvard.edu (G.Pavlov) writes: >In article <4044@batcomputer.tn.cornell.edu>, sparks@batcomputer.tn.cornell.edu (Steve Gaarder) writes: >> >> Worse than that, TK50's are extremely unreliable. I think a lot of the unreliable experiences with tk50 come from the actual tape cartidges and the BSD TMSCP driver. With new tk50 cartidges used on Ultrix 2.0+ systems, they seem to work without hassles. The VS410 CPU (microVAX 2000 and the VAXstation 2000) interfaces to its TK50 (actually a TZK50) through a SCSI interface. The TZK50 or TK50 are are using SCSI already. The drive is hooked up via a 50 pin connector. The 5380 tape controller chip which implements the slave's end of TMSCP is right on the main CPU board. If you want more exact details, order the following tech. manual from your local DEC rep, EK-VTTAA-TM-001 (aka. VAXstation 2000 and MicroVAX-2000 Technical Manual). -- -Edmund C. Lam (University of Waterloo) [network wish bone]!watmath!grand!eclam