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

Conference cookie::archive_backup

Title:	Archive/Backup

Moderator:	COOKIE::MHUAIG

Created:	Wed Sep 08 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	479
Total number of notes:	2283

442.0. "STORAGE LOAD cancels running ABS job to device" by ATZIS1::KARTNER_M (HOUSTON, we have a problem) Tue Apr 22 1997 04:37

    Hi!
    
    We found problems concerning the combination of ABS Save Requests
    and manually entered STORAGE commands.
    
    Config: VMS  V6.2
    	    MDMS V2.8A
    	    ABS  V2.1
    
    During running a BACKUP job from ABS to device MKB200: a
    STORAGE LOAD MKB200: BCF110 reports no error message but
    the save request is canceled !! 
    
    Is this a known BUG ?
    I don't think that this should be an expected behaviour
    
    								bye
    								Michael

T.R	Title	User	Personal Name	Date	Lines
442.1		COOKIE::MHUA		`Tue Apr 22 1997 09:23`	14
	Hi, Please leave ABS/MDMS to take care of the storage load for ABS backup. Do not try to manipulate media while ABS job is running. The result can be unexpected as you have seen. Please post the save request log. We can probabaly tell more from the log. Did you issue any other storage command (other than load) during the backup? Masami
442.2		COOKIE::MHUA		`Tue Apr 22 1997 10:19`	10
	I just thought of more information to collect. Please give us the exact storage command that was issued. Did you try to load the volume already loaded, or did you try to load a different volume? Is it alpha or VAX system? Masami
442.3		CX3PST::BSS::SAUL		`Tue Apr 22 1997 10:42`	4
	Chances are, the ABS/MDMS load failed because it found the tape device in use or the volume it wanted not in the slot. Check ABS log files for MRD failure errors. Ted
442.4	ABS logfile of running saverequest	ATZIS1::KARTNER_M	HOUSTON, we have a problem	`Wed Apr 30 1997 01:41`	168
	Hi! Following the ABS logfile of the running job. The job was aborted after the system manager entered the mentioned storage load command for a drive allready in use by abs. He recognised his mistake emidately and loaded the volume to another drive. Therefor I don't have a status if the manually ordered LOAD was done correct. But it's a fact, that ABS was aborted by this manual intervention. Is this "intended behaviour" ? thanks Michael $ ! $ exit $ v = f$verify(0) Executing ABS LOGIN.COM Completed execution of ABS LOGIN.COM $ EXIT $! SCHEDULER$SHELL.COM -- shell for executing Scheduler jobs $! POLYCENTER Scheduler V2.1 $GOTO Start ! Avoid writing copyright all over the place $Start: $! $ nsched_saved_verify = f$verify(0) $ if f$mode() .eqs. "BATCH" then nsched_batch_job_number = p1 $ run nsched$:scheduler$doo_command "@abs_system:coordinator.com 1C9C8623-A1C8-11D0-B276-414E48543032" Executing, output follows : ------------------------------------------------------ --------------------------------------------------------------- Starting New Request at 18-APR-1997 18:00:35.91 Name: ANUP01_SR_JB_1 UID: 1C9C8623-A1C8-11D0-B276-414E48543032 COORDINATOR: Attempting to allocate volume set BCF082... COORDINATOR: Retiring volume set BCF082 (exceeded consolidation criteria) COORDINATOR: Created new volume set: BCF083 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Failed to mount volume set after 1 attempts COORDINATOR: Facility ABS: ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS COORDINATOR: Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1 COORDINATOR: Facility ABS: ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS COORDINATOR: Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1 COORDINATOR: Facility ABS: ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block COORDINATOR: %SYSTEM-W-NODEVAVL, no device available COORDINATOR: Continuing to retry every 60 seconds... COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: Mounting volume set member: BCF083 RVN 1 COORDINATOR: (Selected drive $4$MKB200:) COORDINATOR: Initializing scratch volume BCF083 %MOUNT-I-MOUNTED, BCF083 mounted on _$4$MKB200: (ANHT02) COORDINATOR: Skipping $4$MKB200: to End of Tape... THREAD #1: Operation #1 starting at 18-APR-1997 18:14:54.21 Data Movement Type: FULL_SAVE Incremental Level: Full Operation Object Set: Object Type: UNIX FILES GTAR Include List: / Exclude List: Archive Information: Storage Class Name: ANUP01_SC_JB_1 Saveset Location: BCF083 Saveset Name: 18APR19971800359. Execution Environment: Name: ANUP01_EE_JB_1 Number of retries: 0 Retry Interval: 0 minute(s) THREAD #1: $ THREAD #1: SET NOON THREAD #1: $ DEFINE SYS$COMMAND sys$input: THREAD #1: $ ubs := $ABS$SYSTEM:ABS$UBS.EXE THREAD #1: $ ubs n?ANUP01 u?"root" l?_MBA8719: - THREAD #1: _$ "d?$4$MKB200:18APR19971800359." - THREAD #1: _$ af?SL THREAD #1: S os?"UNIX" s - THREAD #1: _$ "c?ABSgtar -cvPGpb20 --totals --same-owner -l --ignore-failed-read -T /.ABSinclude THREAD #1: s_1 -X /.ABSexcludes_1 -f - -N @1970-1-2@ /" THREAD #1: %ABS-I-STARTED, ubs agent is started THREAD #1: %ABS-F-QIOFAIL qio completion error 596 THREAD #1: %SYSTEM-F-VOLINV, volume is not software enabled THREAD #1: %ABS-F-QIOWERR Unexpected error from QIOW 596 THREAD #1: %ABS-F-NOTOPEN write_block_synch: device not opened or eot state THREAD #1: %ABS-F-NOTOPEN write_block_synch: device not opened or eot state THREAD #1: %ABS-F-NOTOPEN Write_tm called with device not opened or eot THREAD #1: %ABS-F-NOTOPEN Write_tm called with device not opened or eot THREAD #1: %ABS-F-NOTOPEN Skip_tm called with device not opened or eot THREAD #1: %ABS --UBS FAILURE-- THREAD #1: $ COORDINATOR: Retiring volume set BCF083 (due to fatal error during save) COORDINATOR: Dismounting volume set member: BCF083 RVN 1 THREAD #1: Agent retry exhausted THREAD #1: Normal successful completion COORDINATOR: Invalid volume set name in Storage Class COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: %ABS --UBS FAILURE-- COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 1285, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1 COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 2019, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1 COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 1259, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1 COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 1033, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1 COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 6781, File = RESD$:[SRC]SLS_SERVICES.C;1 COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name in Storage Class COORDINATOR: Line = 10160, File = RESD$:[SRC]SLS_SERVICES.C;1 COORDINATOR: Final status is Invalid volume set name in Storage Class %SYSTEM-F-OPINCOMPL, operation is incomplete ABS job terminated at 18-APR-1997 18:29:48.53 Accounting information: Buffered I/O count: 2946 Peak working set size: 12528 Direct I/O count: 678 Peak page file size: 66272 Page faults: 1640 Mounted volumes: 2 Charged CPU time: 0 00:00:10.13 Elapsed time: 0 00:29:48.37 RFC-822-headers: Received: from reoexc1.reo.dec.com by rg71rw.reo.dec.com (PMDF V5.0-7 #15552) id <[email protected]> for [email protected]; Wed, 30 Apr 1997 07:22:01 +0100 Received: by reoexc1.reo.dec.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63) id <[email protected]>; Wed, 30 Apr 1997 07:23:36 +0100 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63
442.5		COOKIE::MHUA		`Wed Apr 30 1997 09:46`	6
	I did not think the type of dvice used in the operation was mentioned in the previous notes. Please supply us with the information. Also how the device is connected (if it's through a controller). Masami
442.6		COOKIE::MHUA		`Wed Apr 30 1997 11:18`	23
	I just talked to an SLS/MDMS engineer. He says that with sufficient privs, it is possible that STORAGE LOAD command will UNLOAD what is in the drive and successfully LOAD the specified media. This must have happened at some timing that ABS has the media loaded and initialized (the log says), but before any backup data started to come in for write. ABS thought one cartridge that it initialized was in the drive, but it got swapped around underneath it without its knowledge. This tape was not a newly initialized tape as it expected and it caused a fatal error. Please advice the customer that the drive should be left alone while the ABS operation is using. If the STORAGE LOAD happened after the drive started to write for backup data already, it should fail. The operation just hit the small timing window. However, do not take any chances and please leave the drive alone. Thanks, Masami