[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

542.0. "backup creation date" by MDR01::NIEVES (MCS Madrid) Mon Apr 28 1997 12:24

    Hi,
    
    after the execution of both image backup and incremental backups
    with VMS 6.2, the customer checks doing dir/full, that some of the save 
    sets have creation date and others don't. He thinks this is very
    strange and asks why are there some save sets with no creation date.
    
    This is part of the dir/full:
    
    APLICACIONES_COM.BCK 		File id: (93,5,0)
    Size:	4183515/4183517  Owner: [1,1]
    Created:	<None specified>
    Revised:	27-APR-1997 04:48:45.71 (2)
    Expires:	<None specified>
    Backup:	<No backup recorded>
    Effective:  <None specified>
    Recording:  <None specified>
    File organization: 	Sequential
    File attributes:	Allocation: 4183517, Extend:0 , Global buffer
    count: 0
    Record format:	Fixed lenght 32256 byte records
    Record attributes:	None
    RMS attibutes:	None
    Journaling enabled:	None
    File pro:...
    Access ...
    
    
    He executes two types of backup, image and incremental, from a batch
    procedure, and the save set is created on another disk, not a tape.
    The backup command is more or less:
    
    image:
    
    $ BACKUP/IMAGE/VERIFY/RECORD/IGNO=INTERLOCK/LIST='MI_DIR'IMA.LIS 
    _$ APLICACIONES: BACKUPS:[BCK]APLICACIONES_COM.BCK/SAV
    
    
    incremental:
    
    $
    BACKUP/SINCE=BACKUP/VERIFY/RECORD/IGNORE=INTERLOCK/LIST='MI_DIR'INC.LIS
    APLICACIONES:[000000...] BACKUPS:[BCK]APLICACIONES_INC.BCK/SAV
    
    
    Thanks in advance,
    
    Nieves
    
T.RTitleUserPersonal
Name
DateLines
542.1Check ECO, Then IPMTXDELTA::HOFFMANSteve, OpenVMS EngineeringMon Apr 28 1997 12:414
   Look at the current BACKUP kit for V6.2, and -- if it does not appear
   to address this -- please log an IPMT.