| Title: | Archive/Backup |
| Moderator: | COOKIE::MHUA IG |
| 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 |
Hi,
I have some problems restoring from a volume set (VS). The VS (SLS044)
consists of 4 Tapes (SLS044, SLS045, SLS046, SLS047). The current
used VS is SLS048. Restoring from SLS048 makes no problems.
Thomas
Here is the log-file:
$ SET noVERIFY
%SET-W-NOTSET, error modifying DKA0:
-SET-E-INVDEV, device is invalid for requested operation
Executing ABS LOGIN.COM
Completed executing of ABS LOGIN.COM
"@abs_system:coordinator.com 8A67D8DC-D119-11D0-8001-AA000400110C" Executing, o
------------------------------------------------------
---------------------------------------------------------------
Starting New Request at 20-MAY-1997 14:01:32.25
Name: AS2
UID: 8A67D8DC-D119-11D0-8001-AA000400110C
COORDINATOR: Looking up WAK005$DKA200:[PCCOMMON.AS...]*.*;* in catalog ABS_CAT
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Failed to allocate volume set for restore after 1 attempts
COORDINATOR: Continuing to retry every 60 seconds...
COORDINATOR: Attempting to allocate volume set SLS044...
...
COORDINATOR: Failed to allocate volume set for restore after 75 attempts
COORDINATOR: Continuing to retry every 60 seconds...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Attempting to allocate volume set SLS044...
COORDINATOR: Failed to access Storage Class
COORDINATOR: Facility ABS: ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storag
COORDINATOR: Line = 736, File = RESD$:[SRC]COORDINATOR.C;1
COORDINATOR: Facility ABS: ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storag
COORDINATOR: Line = 370, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
COORDINATOR: Facility ABS: ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storag
COORDINATOR: Line = 643, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1
COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name
COORDINATOR: Line = 1987, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR: Facility ABS: ABS_SLS_INVLD_VOLUME_SET, Invalid volume set name
COORDINATOR: Line = 2851, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Line = 2851, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Line = 10214, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Line = 927, File = RESD$:[SRC]VOLSET_MANAGEMENT.C;1
COORDINATOR: Facility ABS: ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific err
COORDINATOR: %SLS-F-NOTFREE, requested volume is not free
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Facility ABS: ABS_SLS_VSET_ALLOC_FAILED, Failed to allocate volu
COORDINATOR: Line = 10214, File = RESD$:[SRC]SLS_SERVICES.C;1
...
...
COORDINATOR: %SLS-F-NOTFREE, requested volume is not free
COORDINATOR: Final status is Failed to access Storage Class
%SYSTEM-F-OPINCOMPL, operation is incomplete
ABS job terminated at 21-MAY-1997 00:10:06.82
Accounting information:
Buffered I/O count: 315069 Peak working set size: 18928
Direct I/O count: 42776 Peak page file size: 74656
Page faults: 2072 Mounted volumes: 0
Charged CPU time: 0 00:06:24.14 Elapsed time: 0 10:08:41.71
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 464.1 | More input | STOWKS::SLUIS | Hans van Sluis - StorageWorks Engineering Support Europe- DTN 889 9526 | Wed May 21 1997 03:59 | 3 |
Thomas, Can you post the output of STORAGE SHOW VOLUME SLS044 | |||||
| 464.3 | Volume set | SUOBOS::RUCKH | Wed May 21 1997 06:15 | 87 | |
Hi,
here is the output from STORAGE SHOW VOL SLS044
Thomas
Volume: SLS044 Owner: WAK001::ABS
Format: BACKUP Brand:
Allocated: 29-APR-1997 08:57 Scratch: 25-JUN-1997 05:17
Purchased: 23-JUL-1996 09:14 Cleaned: 23-JUL-1996 09:14
Media type: TZ877 Length: 0
Mounts: 3 UIC: [ABS]
Location: WAK Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: ALLOCATED
Next volume: SLS045 Previous: *none*
Pool: MAG07 Rec len: 0 Block factor: 0
Initialized: 29-APR-1997 08:57 Density: COMP
Slot number:
Side: Other side:
Jukebox / slot: WAK_JUKEBOX1 / 2
Drive: *WAK005::WAK005$MKA400
Volume is in a jukebox slot.
Volume is bound to slot 2 in magazine WAKMAG07
Volume: SLS045 Owner: WAK005::ABS
Format: BACKUP Brand:
Allocated: 1-MAY-1997 22:46 Scratch: 25-JUN-1997 05:17
Purchased: 23-JUL-1996 09:14 Cleaned: 23-JUL-1996 09:14
Media type: TZ877 Length: 0
Mounts: 1 UIC: [ABS]
Location: WAK Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: ALLOCATED
Next volume: SLS046 Previous: SLS044
Pool: MAG07 Rec len: 0 Block factor: 0
Initialized: 29-APR-1997 08:57 Density: COMP
Slot number:
Side: Other side:
Jukebox / slot: WAK_JUKEBOX1 / 3
Drive: **WAK005::WAK005$MKA400
Volume is in a jukebox slot.
Volume is bound to slot 3 in magazine WAKMAG07
Volume: SLS046 Owner: WAK005::ABS
Format: BACKUP Brand:
Allocated: 8-MAY-1997 22:35 Scratch: 25-JUN-1997 05:17
Purchased: 23-JUL-1996 09:14 Cleaned: 23-JUL-1996 09:14
Media type: TZ877 Length: 0
Mounts: 1 UIC: [ABS]
Location: WAK Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: ALLOCATED
Next volume: SLS047 Previous: SLS045
Pool: MAG07 Rec len: 0 Block factor: 0
Initialized: 29-APR-1997 08:57 Density: COMP
Slot number:
Side: Other side:
Jukebox / slot: WAK_JUKEBOX1 / 4
Drive: *WAK005::WAK005$MKA400
Volume is in a jukebox slot.
Volume is bound to slot 4 in magazine WAKMAG07.
Volume: SLS047 Owner: WAK010::ABS
Format: BACKUP Brand:
Allocated: 15-MAY-1997 06:53 Scratch: 25-JUN-1997 05:17
Purchased: 23-JUL-1996 09:14 Cleaned: 23-JUL-1996 09:14
Media type: TZ877 Length: 0
Mounts: 1 UIC: [ABS]
Location: WAK Protection: S:RW,O:RW,G:R,W:
Notes:
Offsite: Onsite:
IO Errors: 0 Flag: ALLOCATED
Next volume: *none* Previous: SLS046
Pool: MAG07 Rec len: 0 Block factor: 0
Initialized: 29-APR-1997 08:57 Density: COMP
Slot number:
Side:
Jukebox / slot: WAK_JUKEBOX1 / 5
Drive: *WAK005::WAK005$MKA400
Volume is in a jukebox slot.
Volume is bound to slot 5 in magazine WAKMAG07.
| |||||
| 464.2 | see 465.0 | SUOBOS::RUCKH | Wed May 21 1997 06:17 | 5 | |
Hi,
I'm sorry i opened a new topic (465)
Thomas
| |||||
| 464.4 | reply moved | COOKIE::MHUA | Wed May 21 1997 10:17 | 5 | |
The note posted in 465.0 was moved as 464.3 to keep the discussion
trackable.
Masami
| |||||
| 464.5 | More information and questions | COOKIE::MHUA | Wed May 21 1997 10:36 | 20 | |
Thomas,
Please post the show/full output of the restore request, storage class
and execution environment involved.
Also, please execute the following command to see ABS internal volume
set data structure. Make sure that the volume name is quoted and
uppercased.
$storage show volume "&+SLS044"
The diagnostic dump indicates that attempt to allocate the "volume set"
for restore failed after 120 attempts. ABS internally retries to wait
for the volume set ( and the volume to restore ) to be available. Was
there another save ore restore using this volume set going on at the
time of restore???
Thanks,
Masami
| |||||
| 464.6 | not free ? | SUOBOS::RUCKH | Thu May 22 1997 01:53 | 243 | |
Hi Masami,
yes there is another restore request from the same VS to test if a restore
of a single file works. But the log-file shows the same result. After many
hours (with 6 hours CPU-time and about 40000 BIO) I got the same error-message.
In the meanwhile the regular saves and one other restore from the actual tape
has finished without errors. What I don't understand is the message
"%SLS-F-NOTFREE, requested volume is not free".
Thomas
here are some more information:
Restore Request
Name - AS2
Version - 1
UID - 8A67D8DC-D119-11D0-8001-AA000400110C
Movement Type - SELECTIVE_RESTORE
Data Object Set
Movement Criteria - OVERLAP
Commit Granularity - KEEP_PARTIAL
Node Name - WAK005
Include Spec - WAK005$DKA200:[PCCOMMON.AS...]*.*;*
Exclude Spec -
Type Name - VMS Files
Data Movement Flags - None
File System Options - None
Object Date Options - None
Selection Options - None
Restore Options - RETAIN_EXISTING_VERSIONS
Date Identifier - CREATION
Low Limit Date - 17-NOV-1858 00:00:00.00
High Limit Date - 17-NOV-1858 00:00:00.00
Output Spec - None
Owner - WAK005::SYSTEM
Access Right - WAK005::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Class Name - CLIENT_SC
Date Archived - 14-MAY-1997 13:00:00.00
Match Criteria - PRECEDING_COPY
Output Spec - None
Execution Envir - DEFAULT_ENV
Wait Flag - NO
Prologue Command - None
Epilogue Command - None
Alt Restore Info - None
Storage Class
Name - CLIENT_SC
Version - 171
UID - E8E7A142-D1B1-11D0-8001-AA000400110C
Node Name -
Archive File System
Primary Archive Location -
Staging Location -
Primary Archive Type - SLS/MDMS
Staging Archive Type - NOT IMPLEMENTED
Staging Retention Period - 17-NOV-1858 00:00:00.00
Owner - WAK009::SYSTEM
Access Right - WAK009::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK009::ABS
Access Granted - READ, WRITE, SET, EXECUTE
Access Right - WAK008::ABS
Access Granted - READ, WRITE, SET, EXECUTE
Access Right - WAK008::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK001::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK001::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK005::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK005::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK006::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK006::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK010::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK010::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Tape Pool - MAG07
Volume Set Name - SLS042
Retention Criteria
Number Of Copies - 4
Retention Period - 40 00:00:00.00
Consolidation Criteria
Count - 0
Capacity - 0
Size - 0
Interval- 7 00:00:00.00
Catalog Name - ABS_CATALOG
Retain When Idle Flag - NO
Streams - 1
Media Management Info
Media Location - WAK
Media Type - tz877
Device Name - None
Execution Environment
Name - DEFAULT_ENV
Version - 2
UID - CCB2CD20-BACA-11CF-8001-AA000400110C
Data Safety Options - FULL_DATA_VERIFICATION, XOR_REDUNDANCY_GROUPS, CRC_VER
IFICATION
Listing Option - NO_LISTING
Span Filesystem Options - SPAN FILESYSTEMS
Symbolic Links Option - LINKS_ONLY
Compression Options - None
User Profile
Node - *
Cluster - *
User - ABS
Privs - SETPRV,TMPMBX,OPER,NETMBX
Platform ID - 0
Access Right - None
Owner - WAK009::ABS
Access Right - WAK009::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK008::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK008::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK009::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK010::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK010::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK001::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK001::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK005::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK005::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK006::SYSTEM
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Access Right - WAK006::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION, AT_COMPLETION
Agent Filesystem Options - None
Logging Option - NOT SUPPORTED
Number of Drives - 1
Staging Option - STAGING_ALLOWED
Retry Count - None
Retry Interval - None
Prologue Command - None
Epilogue Command - None
Volume: &+SLS044 Owner: WAK001::ABS
Format: BACKUP Brand:
Allocated: 20-MAY-1997 09:18 Scratch: 19-JUN-1997 09:18
Purchased: 29-APR-1997 08:57 Cleaned: 29-APR-1997 08:57
Media type: TZ877 Length: 0
Mounts: 0 UIC: [ABS]
Location: %ABS_VOLSET% Protection: S:RW,O:RW,G:R,W:
Notes: 00001B7F
Offsite: Onsite:
IO Errors: 4 Flag: ALLOCATED
Next volume: *none* Previous: *none*
Pool: %ABS_VOLSET% Rec len: 0 Block factor: 0
Initialized: 29-APR-1997 08:57 Density: 00000000
Slot number:
Side: Other side:
Jukebox / slot: /
Drive:
Volume is not in a jukebox.
Volume is not in a magazine.
| |||||
| 464.7 | COOKIE::MHUA | Thu May 22 1997 14:39 | 55 | ||
Thomas,
SLS-F-NOTFREE message comes from "&+SLS044" record being allocated.
It is the record internally controlled by ABS.
1. See if coordinator cleanup process is running. Do show system and see
if you have ABS$COORD_CLEAN process name on the list.
2. Do the search of the coordinator cleanup data file and see if
any of the involved volumes are marked in this data file.
$search abs$system:coord_cleanup.dat sls044
$search abs$system:coord_cleanup.dat sls045
$search abs$system:coord_cleanup.dat sls046
$search abs$system:coord_cleanup.dat sls047
3. shutdown/restart ABS. If coordinator cleanup process is not
running, you need to do this. Also, in case this process is stalled
for some reason, this will clear it out.
You want to trun on reply/enable=tape before restart.
4. Monitor the log file from coordinator cleanup and see if any
cleanup activity is happening.
It will log what failed/aborted requests left some resources to
cleanup.
$ v = f$verify(0)
Executing ABS LOGIN.COM
Completed execution of ABS LOGIN.COM
$ EXIT
--------- 20-MAY-1997 10:20:57.82 -----------------
ABS_CLEANUP: Cleanup performed for aborted job
Request Name: HP1
Scheduler Job: 40861
Deleted PID: 38606AD0
--------- 20-MAY-1997 10:51:15.07 -----------------
ABS_CLEANUP: Cleanup performed for aborted job
Request Name: HP1
Scheduler Job: 40935
Deleted PID: 386034DA
If the cleanup activities are going on, you will get opcom messages in
tape class also.
******************************
If above suggestion does not work, I need to send you some utilities
to clear this record to meke it work. Please let us know.
Masami
| |||||
| 464.8 | need utilities | SUOBOS::RUCKH | Fri May 23 1997 02:35 | 8 | |
Hi Masami,
on two nodes there are entries in the coord_cleanup.dat files from
volume SLS044. No more cleanup activity is happening after
shutdown/restart ABS.
Please send me some utilities to clear the record.
Thomas
| |||||
| 464.9 | solved | COOKIE::MHUA | Tue May 27 1997 09:46 | 10 | |
Update:
I instructed Thomas to issue
$storage deallocate/user=abs "&+SLS044"
command to release this record and restore started to work after that.
Masami
| |||||