[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

407.0. "CTRL-O looses dir info during SAB" by TAV02::CHAIM (Semper ubi Sub ubi .....) Wed Apr 02 1997 02:27

OpenVMS V6.2

A customer has described the following behaviour:

He booted standalone backup and issued backup/image/log. At that point he
starts getting the full file specification for each file being processed. At
some point he issued CTRL-O on the console and the CTRL-O again to resume the
display. From this point on he claims that he no longer received the full file
specification, but ONLY [] with the directory information normally contained
within the [] missing.

We both tried this with full VMS running and were unable to reproduce this. 

Unfortunatley, I do not currently have a system on which to try this.

Obviously this has no affect on the actual content of the backup saveset, but
the customer would like to understand what he has experienced.

Thanks,

Cb.

T.R	Title	User	Personal Name	Date	Lines
407.1		AUSS::GARSON	DECcharity Program Office	`Wed Apr 02 1997 03:28`	8
	re .0 Of course backup/image, standalone or otherwise, can save files that are not in a directory and which are indeed logged as []NAME.TYPE;N so I would start by doing a BACK/LIS on the backup to confirm that you are not experiencing this situation. VAX or Alpha?
407.2	ANALYZE the source-input disk structure...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Wed Apr 02 1997 10:38`	8
	.1: Of course backup/image, standalone or otherwise, can save files that .1: are not in a directory and which are indeed logged as []NAME.TYPE;N .1: so I would start by doing a BACK/LIS on the backup to confirm that you .1: are not experiencing this situation. Also consider ANALYZE/DISK [/REPAIR] on the BACKUP source-input disk, and see how many files find their way into [SYSLOST]....
407.3	Alias problem?	SWETSC::WESTERBACK	Panta rei	`Thu Apr 03 1997 04:58`	24
	File specs starting with [] are standard when a listing an image backup of a system disk which has the infamous (and common) alias file problem, which is shown if you do $ sh dev/files sys$sysdevice it should give output like this .... 00000000 [VMS$COMMON.SYS$LDR]SYS.EXE;2 00000000 [VMS$COMMON.SYS$LDR]EXEC_INIT.EXE;2 .... If you have the error it says something else, I think it was .... 00000000 [SYSCOMMON.... instead of VMS$COMMON Solution found in Release notes and many notes in here. Rgds, Hans
407.4	BACKUP/[NO]ALIAS	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Thu Apr 03 1997 10:37`	14
	I'm not sure the alias back-link problem is related to this. The alias backlink problem referenced in .3 was a result of having one of the alternate backlinks listed as "primary": [VMS$COMMON.SYS$LDR] and [SYS0.SYSCOMMON.SYS$LDR] are the same directory file, after all. There is a way to reduce the total size of a BACKUP that involves ignoring the contents of the alternate backlinks. This reduces the size of the BACKUPs of disks with backlinks, but it also means that any /SELECT file-oriented restorations will operate only if the primary path (link) is specified. See BACKUP/[NO]ALIAS.