HP OpenVMS Systems

BACKUP and OpenVMS V6.2 (and later)?

» close window

The Question is:

 
I have a client that upgraded from VMS 5.5-2 to VMS 6.2 . The problem is
with backups and the TLZ06 tape drive. I had to remove a density qualifier
in the init command, then remove a /record qualifier from the backup
command. The disk being backuped is a
shadow member I dismounted then mounted with the /over=id qualifier. It does
not seem to "fit everything on the tape anymore".
 
I then copied the data to another disk. I did an image backup as a batch
job. It did work, but it took 3 hrs.
 
The only thing that changed was the VMS upgrade, which the client did.
 
so my 2 problems are:
1) how can I "speed up the backup". The data does fit on the tape.
2) is there anthing I need to do different with 6.2 and dismounted shadow
disk ??
 
p.s. If you are the person in the picture, Jim, my wife jill wanted to say
hi.
 
thanks
 
 

The Answer is :

 
  The exact BACKUP command used -- working and failing -- would be very
  useful, as would the specific error message(s) generated.  Without this
  information, the OpenVMS Wizard is left to guess.
 
  The OpenVMS Wizard would expect that a command such as:
 
    BACKUP ddcu: -
      mmcu:saveset.bck/SAVE/REWIND/LABEL=(x,y,z) -
      /IGNORE=(LABEL,NOBACKUP)
 
  would work in this situation.
 
  There are changes to the processing of incremental BACKUPs, please see
  the V6.2 release notes for details.  In particular, the same situation
  referenced to in the release notes around PATHWORKS files has been found
  to arise in other situations.  To ensure restoration, files below any
  altered directories are saved as part of an incremental save.
 
  The OpenVMS Wizard will assume that the disk is the system disk, and
  that switching to /NOIMAGE and over to a file-oriented BACKUP caused
  multiple copies of the file data to be transfered to tape.
 
  The /DENSITY qualifier is intended only for magtapes on OpenVMS VAX.
 
  Experimentation with the block size qualifier and particularly with
  the correct set of process quotas -- specified in the section on BACKUP
  in the system manager's manual section -- can help you speed the BACKUP
  processing.
 
  The use of /NOALIAS can greatly reduce the size of /IMAGE BACKUPs of the
  OpenVMS system disk or other disks with alias entries, but please be
  sure you understand the full ramifications of this qualifier before you
  should need to perform a restoration of specific files.  Selective file
  restoration is still possible, and BACKUP will completely restore the
  alias entries as part of an /IMAGE restoration of a /NOALIAS saveset.
 
  Also please consider acquiring and applying the available BACKUP ECO,
  and examining the documentation for information on enhancements made to
  the BACKUP to allow selection of the processing of individual files.
  (These changes were made to BACKUP in more recent OpenVMS versions, and
  have been backported to older OpenVMS releases.)
 
	--
 
  The OpenVMS Wizard has no idea who is in the picture at the OpenVMS Ask
  The Wizard web site.  Sorry, Jill.
 

  

     

     
answer written or last revised on ( 28-MAY-1999 )
     
» close window