From:	CSBVAX::MRGATE!RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP 11-AUG-1988 18:31
To:	ARISIA::EVERHART
Subj:	vms 5.0 backup change


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Wed, 10 AUG 88 09:55:09 PDT
Received: from GTRI01.GATECH.EDU by KL.SRI.COM with TCP; Wed, 10 Aug 88 09:37:32 PDT
Received: from GTRI01.GATECH.EDU by GTRI01.GATECH.EDU ; Wed, 10 Aug 88 11:53:39 EDT
Received: by GTRI01 (Mailer X1.25) id 0006; Wed, 10 Aug 88 11:53:29 EDT
Date:         Wed, 10 Aug 88 11:39:12 EDT
From:         Mike Sieweke <MSIEWEKE@GTRI01>
Subject:      vms 5.0 backup change
To:           info-vax@kl.sri.com

Just a little bit of info about backup under vms 5.0.  This is probably
in the release notes, but it bit me anyway.

In 5.0 backup checks to see if the tape label matches the save set name.
If the label doesn't match, backup will (by default) send a request to
the tape operator requesting that the correct tape be loaded.  The user
won't know that there is a problem.

For example,
$ mount/for mua0 tape
$ backup [...] mua0:mybackup.bck

At this point a message goes to the tape operator asking for a tape labeled
"myback".  Or the operator can specify "overwrite", and things go as
they should.  However, if you don't have a tape operator, the backup
command will wait and wait and wait...

What you need to do is to specify "/ignore=label" on the backup command.
With this qualifier, backup will operate as it did before 5.0

I hope this helps.

Mike Sieweke <msieweke@gtri01>             BitNet
          or <sysmike@bwms.gatech.edu>     InterNet
Georgia Tech Research Institute
Atlanta, Georgia