ANR8877E problem with WORM tapes

karvan31

Newcomer
Joined
Mar 21, 2020
Messages
1
Reaction score
0
Points
0
Hi,

I have a TSM 7.1.4.100 server and it is connected to a TS3310 library with 4 LTO-5 drives. I have devclass with worm=yes.

tsm: >q dev BLTO_WORM f=d

Device Class Name: BLTO_WORM
Device Access Strategy: Sequential
Storage Pool Count: 2
Device Type: LTO
Format: DRIVE
Est/Max Capacity (MB):
Mount Limit: DRIVES
Mount Wait (min): 60
Mount Retention (min): 30
Label Prefix: ADSM
Library: BTS3310
Directory:
Server Name:
Retry Period:
Retry Interval:
Shared:
High-level Address:
Minimum Capacity:
WORM: Yes
Drive Encryption: Allow
Scaled Capacity:
Primary Allocation (MB):
Secondary Allocation (MB):
Compression:
Retention:
Protection:
Expiration Date:
Unit:
Logical Block Protection: No
Last Update by (administrator):
Last Update Date/Time: 04/14/2014 17:05:44

This devclass contains storage pool:
tsm: >q stg B_FILE_TAPE_WORM

Storage Device Storage Estimated Pct Pct High Low Next Stora-
Pool Name Class Name Type Capacity Util Migr Mig Mig ge Pool
Pct Pct
----------- ---------- --------- ---------- ----- ----- ---- --- -----------
B_FILE_TAP- BLTO_WORM DEVCLASS 206,846 G 29.9 53.5 90 70
E_WORM


This stg contains WORM tapes (it is OK) but there are also two LTO-5 tapes (it isn't OK).
Documentation said that: „A storage pool can consist of either WORM or RW media, but not both.”


tsm: >q vol stg=B_FILE_TAPE_WORM

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
E_WORM
PLB024W4 B_FILE_TAP- BLTO_WORM 883.3 G 99.3 Full
E_WORM
PLB025W4 B_FILE_TAP- BLTO_WORM 774.9 G 100.0 Full
E_WORM
PLB026L5 B_FILE_TAP- BLTO_WORM 2.9 T 12.6 Filling
E_WORM
PLB027L5 B_FILE_TAP- BLTO_WORM 1.1 T 0.0 Full

E_WORM
PLB032W5 B_FILE_TAP- BLTO_WORM 2.9 T 19.3 Filling
E_WORM
PLB034W5 B_FILE_TAP- BLTO_WORM 2.9 T 49.4 Filling


tsm: >q libvol

Library Name Volume Name Status Owner Last Use Home Device
Element Type
------------ ----------- ---------------- ---------- --------- ------- ------
BTS3310 PLB024W4 Private(Worm) TSM_01 Data 4,143
BTS3310 PLB025W4 Private(Worm) TSM_01 Data 4,147
BTS3310 PLB026L5 Private TSM_01 4,216 LTO
BTS3310 PLB027L5 Private TSM_01 4,211 LTO

BTS3310 PLB032W5 Private(Worm) TSM_01 Data 4,176
BTS3310 PLB034W5 Private(Worm) TSM_01 Data 4,178


tsm: >q con PLB027L5

Node Name Type Filespace FSID Client's Name for File
Name
--------------- ---- ---------- ---- --------------------------------------
PL136RMN141 Arch / 1 /var
PL136RMN141 Arch / 1 /var/log


When I try export some nodes which are located on LTO-5 volumes I receive error:

03/20/2020 08:02:54 ANR8877E Volume PLB026L5 is incompatible type with device
class BLTO_WORM in library BTS3310. (PROCESS: 11165)


Anybody know how can I export these nodes and why these volumes were used??


Thank for your help.
 
I don't have any experience with WORM vol's so with that in mind: Perhaps best to get a ticket going with the IBM team before trying anything.

Could always do a q vol f=d and see when they were wrote to, may tell you who last updated them.
Wonder if you could use move data <volume> to empty? Or at least get the data off and onto a real worm volume?

Sorry, just no knowledge of WORM media and device classes.
 
Back
Top