[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

134.0. "AXP 6.1 igno=nobackup not working" by ALFSS2::GRINNELL_M () Mon Feb 03 1997 18:25

    A customer is running AXP 6.1 and when attempting to backup a file
    marked nobackup using the backup/igno=nobackup command the files are
    still not getting backed up. He was trying to backup sysdump.dmp 
    because the system crashed. I had him try the same thing on a text file
    with the same results. I was unable to duplicate the problem. His
    backup image matched my own. Looking for suggestions.
    
    image name: "BACKUP"
    
    image file identification: "AXP V6.1"
                    image file build identification: "X5SC-SSB-0000"
                    link date/time:  2-APR-1994 07:42:17.81
                    linker identification: "T11-11"
    
    Michael

T.R	Title	User	Personal Name	Date	Lines
134.1		POMPY::LESLIE	[email protected] as of Feb 14	`Tue Feb 04 1997 02:45`	1
	/ignore=(nobackup, interlock)
134.2	Error Messages? Exact BACKUP Command?	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Feb 04 1997 09:04`	23
	re: .-1 /IGNORE=(INTERLOCK,NOBACKUP) would override any access interlocks, but I'd not expect problems with a newly-created `generic' text file... : A customer is running AXP 6.1 and when attempting to backup a file : marked nobackup using the backup/igno=nobackup command the files are : still not getting backed up. Classic question: what's the complete BACKUP command being used by the customer? And how does the customer know the file(s) are not getting copied? : He was trying to backup sysdump.dmp because the system crashed. For this specific purpose, consider using the SDA> COPY command. (It is another means of relocating the system dump from the dump file or -- if that's where it's written -- from the page file.) : I had him try the same thing on a text file with the same results. Are there any error messages reported?
134.3	igno=nobackup	ALFSS2::GRINNELL_M		`Tue Feb 04 1997 09:49`	6
	I found the problem. The customer had backup.exe installed. I had him install remove and the backup/igno=nobackup works again. Must have been corrupted. Thanks for your reply, Michael
134.4	Not Likely INSTALL, Not Likely Corruption	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Tue Feb 04 1997 10:02`	13
	: I found the problem. The customer had backup.exe installed. I had : him install remove and the backup/igno=nobackup works again. Must : have been corrupted. Huh? INSTALL should not corrupt an image file. And BACKUP is installed by default on the local Alpha systems. And a corrupted image file typically does not behave `rationally' -- image file corruptions usually cause more obvious and more dramatic errors. I'd expect there was another cause -- customer error?. (Given that BACKUP will likely be reinstalled on the next system reboot, I'd keep looking otherwise.)
134.5		AUSS::GARSON	DECcharity Program Office	`Tue Feb 04 1997 16:51`	7
	re .last few The explanation leaves something to be desired. In any case you might want to comment on what INSTALL qualifiers had been used. The use of INSTALL can cause an unexpected version of BACKUP.EXE to be in use if there is more than one but then you still have to explain the existence and behaviour of the rogue version.