Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!nike!ucbcad!ucbvax!CS.UCL.AC.UK!MACALLSTR%vax1.physics.oxford.ac.uk
From: MACALLSTR%vax1.physics.oxford.ac.uk@CS.UCL.AC.UK
Newsgroups: mod.computers.vax
Subject: Backup continuation tapes.
Message-ID: <8609032108.AA09255@ucbvax.Berkeley.EDU>
Date: Wed, 3-Sep-86 17:08:56 EDT
Article-I.D.: ucbvax.8609032108.AA09255
Posted: Wed Sep  3 17:08:56 1986
Date-Received: Thu, 4-Sep-86 03:42:56 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 15
Approved: info-vax@sri-kl.arpa

We've been using BACKUP and writing to several continuation tapes. We have
 restored data on several occasions, including full disk restores, without
 trouble.

In our regular backup procedures I specify /DENSITY in both the MOUNT and
 BACKUP commands. I also use the /LABEL qualifier in the BACKUP command
 and allow BACKUP to write its own continuation labels : our local software
 keeps track of which 'sticky label' relates to which backup tape. 

Some general advice for anyone writing tapes on any system. When writing tapes
 specify the DENSITY wherever a command allows. My past experience has shown
 this is the only way to GUARANTEE that your tape is being written at the
 particular density. Software/hardware bugs/defaults can make the outcome
 uncertain. Reading tapes, provided the drive supports the particular density,
 is usually more reliable.