Results 1 to 15 of 15
  1. #1
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Reclamation issue new to TSM please help out

    Hi,

    When I am running reclamation (reclaim stgpool OFFSITE-BACKUP thres=90)
    I am getting the below error.
    ANR1082E Space reclamation is ended for volume 000079L3.
    There is an insufficient number of mount points available
    for removable media.
    Offsite volume 000109L3 still contains files
    which could not be moved. (SESSION: 468, PROCESS: 81)
    ANR0985I Process 81 for SPACE RECLAMATION running in the
    BACKGROUND completed with completion state FAILURE at
    05:07:34 PM. (SESSION: 468, PROCESS: 81).
    Even when I am running reclamation on copypool-backup I am getting the same error as "
    There is an insufficient number of mount points available
    for removable media."

    Below are some of the outputs.

    tsm: SEADOG>q drive
    Library Name Drive Name Device Type On-Line
    ------------ ------------ ----------- -------------------
    DLT_0 DRIVE2 4MM Yes
    ULT3581_0 DRIVE0 LTO Yes
    ULT3581_1 DRIVE1 LTO Yes
    tsm: SEADOG>q libv
    Library Name Volume Name Status Owner Last Use Home Device
    Element Type
    ------------ ----------- ---------------- ---------- --------- ------- ------
    ULT3581_0 000002L3 Private Data 2
    ULT3581_0 000012L3 Private Data 8
    ULT3581_0 000044L3 Private 6
    ULT3581_0 000045L3 Private Data 3
    ULT3581_0 000072L3 Private Data 4
    ULT3581_0 000083L3 Private Data 7
    ULT3581_0 CLNU64L1 Cleaner 1
    ULT3581_1 000020L3 Private SEADOG 5
    ULT3581_1 000036L3 Private SEADOG Data 8
    ULT3581_1 000037L3 Private SEADOG Data 7
    ULT3581_1 000054L3 Private SEADOG Data 2
    ULT3581_1 000079L3 Private SEADOG 4
    ULT3581_1 000094L3 Private SEADOG Data 6
    ULT3581_1 000103L3 Private SEADOG Data 3
    ULT3581_1 CLNU64L1 Cleaner 1
    tsm: SEADOG>q devclass
    Device Device Storage Device Format Est/Max Mount
    Class Access Pool Type Capacity Limit
    Name Strategy Count (MB)
    --------- ---------- ------- --------- ------ -------- ------
    DBBACKUP Sequential 0 FILE DRIVE 640.0 20
    DBBACKUP- Sequential 0 FILE DRIVE 640.0 20
    _B
    DBBACKUP- Sequential 0 4MM DRIVE DRIVES
    _DLT
    DISK Random 5
    LTOTAPE0 Sequential 1 LTO ULTRI- 1
    UM3C
    LTOTAPE1 Sequential 5 LTO ULTRI- 1
    UM3C

    tsm: SEADOG>q stg offsite-backup f=d
    Storage Pool Name: OFFSITE-BACKUP
    Storage Pool Type: Copy
    Device Class Name: LTOTAPE1
    Estimated Capacity: 6,879,526 G
    Space Trigger Util:
    Pct Util: 0.2
    Pct Migr:
    Pct Logical: 99.5
    High Mig Pct:
    Low Mig Pct:
    Migration Delay:
    Migration Continue: Yes
    Migration Processes:
    Reclamation Processes: 1
    Next Storage Pool:
    Reclaim Storage Pool:
    Maximum Size Threshold:
    Access: Read/Write
    Description: Copy pool for offsite storage
    Overflow Location:
    Cache Migrated Files?:
    Collocate?: Group
    Reclamation Threshold: 100
    Offsite Reclamation Limit: No Limit
    Maximum Scratch Volumes Allowed: 9,999
    Number of Scratch Volumes Used: 52
    Delay Period for Volume Reuse: 0 Day(s)
    Migration in Progress?:
    Amount Migrated (MB):
    Elapsed Migration Time (seconds):
    Reclamation in Progress?: No
    Last Update by (administrator): GOALONSO
    Last Update Date/Time: 06/25/09 16:23:20
    Storage Pool Data Format: Native
    Copy Storage Pool(s):
    Active Data Pool(s):
    Continue Copy on Error?:
    CRC Data: Yes
    Reclamation Type: Threshold
    Overwrite Data when Deleted:

    tsm: SEADOG>q devclass f=d
    Device Class Name: DBBACKUP
    Device Access Strategy: Sequential
    Storage Pool Count: 0
    Device Type: FILE
    Format: DRIVE
    Est/Max Capacity (MB): 640.0
    Mount Limit: 20
    Mount Wait (min):
    Mount Retention (min):
    Label Prefix:
    Library:
    Directory: /tsm/dbbackups
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption:
    Scaled Capacity:
    Last Update by (administrator): ADMIN
    Last Update Date/Time: 04/25/07 16:50:30
    Device Class Name: DBBACKUP_B
    Device Access Strategy: Sequential
    Storage Pool Count: 0
    Device Type: FILE
    Format: DRIVE
    Est/Max Capacity (MB): 640.0
    Mount Limit: 20
    Mount Wait (min):
    Mount Retention (min):
    Label Prefix:
    Library:
    Directory: /tsm_2/dbbackups
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption:
    Scaled Capacity:
    Last Update by (administrator): ADMIN
    Last Update Date/Time: 09/07/07 09:39:35
    Device Class Name: DBBACKUP_DLT
    Device Access Strategy: Sequential
    Storage Pool Count: 0
    Device Type: 4MM
    Format: DRIVE
    Est/Max Capacity (MB):
    Mount Limit: DRIVES
    Mount Wait (min): 2
    Mount Retention (min): 2
    Label Prefix: DRM
    Library: DLT_0
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption:
    Scaled Capacity:
    Last Update by (administrator): ADMIN
    Last Update Date/Time: 10/05/07 14:41:14
    Device Class Name: DISK
    Device Access Strategy: Random
    Storage Pool Count: 5
    Device Type:
    Format:
    Est/Max Capacity (MB):
    Mount Limit:
    Mount Wait (min):
    Mount Retention (min):
    Label Prefix:
    Library:
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption:
    Scaled Capacity:
    Last Update by (administrator):
    Last Update Date/Time: 03/28/07 17:29:32
    Device Class Name: LTOTAPE0
    Device Access Strategy: Sequential
    Storage Pool Count: 1
    Device Type: LTO
    Format: ULTRIUM3C
    Est/Max Capacity (MB):
    Mount Limit: 1
    Mount Wait (min): 60
    Mount Retention (min): 2
    Label Prefix: ADSM
    Library: ULT3581_0
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption: Allow
    Scaled Capacity:
    Last Update by (administrator): ADMIN
    Last Update Date/Time: 05/08/07 22:24:02
    Device Class Name: LTOTAPE1
    Device Access Strategy: Sequential
    Storage Pool Count: 5
    Device Type: LTO
    Format: ULTRIUM3C
    Est/Max Capacity (MB):
    Mount Limit: 1
    Mount Wait (min): 60
    Mount Retention (min): 2
    Label Prefix: ADSM
    Library: ULT3581_1
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption: Allow
    Scaled Capacity:
    Last Update by (administrator): ADMIN
    Last Update Date/Time: 05/08/07 22:24:06

  2. #2
    Moderator mikeymac's Avatar
    Join Date
    Jun 2003
    Location
    Syracuse, NY
    Posts
    893
    Thanks
    8
    Thanked 12 Times in 12 Posts

    Smile

    Welcome to adsm.org, Rkonda!

    It looks like you only have two tape drives.

    Unless all of your onsite data is stored on disk pools, you will require at least two tape drives to perform space reclamation. Are there other processes using a tape drive(s) when you attempt space reclamation? Is a client backup running? A TSM database backup?

    You can enter the command "QUERY MOUNT" to see what tapes are mounted on your drives.

  3. #3
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi Mike

    Yes I have checked with q mount no tapes are mounted.

    Coming to client backups yes they are running but, it will copy contents to desk. Its not using drive when client backups are going on most of the times.

    I am not understanding, even I am facing same issue when I am running reclamation on stg copyppol-backup also.

    Can you please suggest what could be the issue.

  4. #4
    Moderator mikeymac's Avatar
    Join Date
    Jun 2003
    Location
    Syracuse, NY
    Posts
    893
    Thanks
    8
    Thanked 12 Times in 12 Posts

    Talking

    I see that your offsite tape pool is assigned to device class LTOTAPE1. LTOTAPE1 has a mountlimit of 1. (this means that only a single tape can be mounted at any one time). Is your onsite tape pool assigned to LTOTAPE1, too? You probably need to increase your mountlimit to 2, or to the value DRIVES.

    Does this make sense?

  5. #5
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi Mike,

    Offsite tapes are assigned to LTOTAPE1 which is stg offsite-backup

    And onsite tapes belong to LTOTAPE0 which is stg backltotape0

    Onsite we are maintaning two copies here. One is bigbackpool and backltotape0
    other one is copypool-backup.

    bigbackpool and backltotape0 belongs to device class LTOTAPE0
    copypool-backup belongs to device class LTOTAPE1

    When I am running reclamation on offsite-backup previously it was picking up tapes from backltotape0 and use to wright the data in offsite-backup which belongs to LTOTAPE1.

    But this time when I am doing reclamation its asking for tape in copypool-backup and falling with mount point unavailable.

    There is only one drive in each library.

    tsm: SEADOG>q drive
    Library Name Drive Name Device Type On-Line
    ------------ ------------ ----------- -------------------
    DLT_0 DRIVE2 4MM Yes
    ULT3581_0 DRIVE0 LTO Yes
    ULT3581_1 DRIVE1 LTO Yes

    If I increase mount limit it will workout?

    Bec there is only one drive in each library.

    I am not understanding why its asking for copypool-backup tape this time, when I am running reclamation on offsite-backup

    Its falling with same error insufficient number of mount points available, even I am trying to do reclamation on copypoo-backup also.

    Please check below output incase required.

    tsm: SEADOG>q stg
    Storage Device Estimated Pct Pct High Low Next Stora-
    Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
    Pct Pct
    ----------- ---------- ---------- ----- ----- ---- --- -----------
    ARCHIVEPOOL DISK 5.0 M 0.0 0.0 90 70 BACKLTOTAP-
    E0
    BACKLTOTAP- LTOTAPE0 5,738,317 0.2 0.3 90 70
    E0 G
    BACKLTOTAP- LTOTAPE1 7,628,617 0.0 0.0 90 70
    E1 G
    BACKUPPOOL DISK 10.0 M 0.0 0.0 90 70 BACKLTOTAP-
    E0
    BIGARCHPOOL DISK 31 G 66.7 66.7 90 70 BACKLTOTAP-
    E0
    BIGBACKPOOL DISK 31 G 3.1 3.1 20 5 BACKLTOTAP-
    E0
    COPYPOOL-A- LTOTAPE1 7,628,617 0.0
    RCH G
    COPYPOOL-B- LTOTAPE1 5,863,775 0.2
    ACKUP G
    OFFSITE-AR- LTOTAPE1 0.0 M 0.0
    CHIVE
    OFFSITE-BA- LTOTAPE1 6,879,526 0.2
    CKUP G
    SPACEMGPOOL DISK 0.0 M 0.0 0.0 90 70

    please suggest me how can go head with reclamation.

    Thanks in advance

  6. #6
    Member
    Join Date
    Apr 2007
    Posts
    293
    Thanks
    0
    Thanked 2 Times in 2 Posts

    Default

    As per your statement:
    "There is only one drive in each library."

    If you want to do reclamation on tape you should have at least two drives per library. If you're only working with one drive, you should define a temporary disk storage to do the reclamation to tape. It's on the administration guide.


    Thanks,

  7. #7
    Moderator mikeymac's Avatar
    Join Date
    Jun 2003
    Location
    Syracuse, NY
    Posts
    893
    Thanks
    8
    Thanked 12 Times in 12 Posts

    Default

    From your original output, device class LTOTAPE0 has only ONE storage pool associated with it.

    Device Class Name: LTOTAPE0
    Device Access Strategy: Sequential
    Storage Pool Count: 1
    Device Type: LTO
    Format: ULTRIUM3C
    Est/Max Capacity (MB):
    Mount Limit: 1

    Therefore, this statement cannot be true:
    bigbackpool and backltotape0 belongs to device class LTOTAPE0
    Can you post a QUERY STGPOOL BIGBACKPOOL and a QUERY STGPOOL BACKLTOTAPE0?

  8. #8
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi Mike

    tsm: SEADOG>QUERY STGPOOL BIGBACKPOOL
    Session established with server SEADOG: Linux/x86_64
    Server Version 5, Release 5, Level 4.0
    Server date/time: 01/06/10 17:16:39 Last access: 01/06/10 15:44:16

    Storage Device Estimated Pct Pct High Low Next Stora-
    Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
    Pct Pct
    ----------- ---------- ---------- ----- ----- ---- --- -----------
    BIGBACKPOOL DISK 31 G 3.1 3.1 20 5 BACKLTOTAP-
    E0
    tsm: SEADOG>QUERY STGPOOL BIGBACKPOOL f=d
    Storage Pool Name: BIGBACKPOOL
    Storage Pool Type: Primary
    Device Class Name: DISK
    Estimated Capacity: 31 G
    Space Trigger Util: 3.1
    Pct Util: 3.1
    Pct Migr: 3.1
    Pct Logical: 100.0
    High Mig Pct: 20
    Low Mig Pct: 5
    Migration Delay: 0
    Migration Continue: Yes
    Migration Processes: 1
    Reclamation Processes:
    Next Storage Pool: BACKLTOTAPE0
    Reclaim Storage Pool:
    Maximum Size Threshold: 60 G
    Access: Read/Write
    Description:
    Overflow Location:
    Cache Migrated Files?: No
    Collocate?:
    Reclamation Threshold:
    Offsite Reclamation Limit:
    Maximum Scratch Volumes Allowed:
    Number of Scratch Volumes Used:
    Delay Period for Volume Reuse:
    Migration in Progress?: No
    Amount Migrated (MB): 16,995.27
    Elapsed Migration Time (seconds): 866
    Reclamation in Progress?:
    Last Update by (administrator): JKKIERNA
    Last Update Date/Time: 06/11/08 13:01:18
    Storage Pool Data Format: Native
    Copy Storage Pool(s): COPYPOOL-BACKUP
    Active Data Pool(s):
    Continue Copy on Error?: Yes
    CRC Data: Yes
    Reclamation Type:
    Overwrite Data when Deleted:


    tsm: SEADOG>QUERY STGPOOL BACKLTOTAPE0
    Storage Device Estimated Pct Pct High Low Next Stora-
    Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
    Pct Pct
    ----------- ---------- ---------- ----- ----- ---- --- -----------
    BACKLTOTAP- LTOTAPE0 5,738,317 0.2 0.3 90 70
    E0 G
    tsm: SEADOG>QUERY STGPOOL BACKLTOTAPE0 f=d
    Storage Pool Name: BACKLTOTAPE0
    Storage Pool Type: Primary
    Device Class Name: LTOTAPE0
    Estimated Capacity: 5,738,317 G
    Space Trigger Util:
    Pct Util: 0.2
    Pct Migr: 0.3
    Pct Logical: 99.6
    High Mig Pct: 90
    Low Mig Pct: 70
    Migration Delay: 0
    Migration Continue: Yes
    Migration Processes: 1
    Reclamation Processes: 1
    Next Storage Pool:
    Reclaim Storage Pool: BACKLTOTAPE1
    Maximum Size Threshold: No Limit
    Access: Read/Write
    Description:
    Overflow Location:
    Cache Migrated Files?:
    Collocate?: Group
    Reclamation Threshold: 100
    Offsite Reclamation Limit:
    Maximum Scratch Volumes Allowed: 9,999
    Number of Scratch Volumes Used: 25
    Delay Period for Volume Reuse: 0 Day(s)
    Migration in Progress?: No
    Amount Migrated (MB): 0.00
    Elapsed Migration Time (seconds): 0
    Reclamation in Progress?: No
    Last Update by (administrator): GOALONSO
    Last Update Date/Time: 06/02/09 15:52:50
    Storage Pool Data Format: Native
    Copy Storage Pool(s):
    Active Data Pool(s):
    Continue Copy on Error?: Yes
    CRC Data: Yes
    Reclamation Type: Threshold
    Overwrite Data when Deleted:

  9. #9
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Sorry yes BIGBACKPOOL belongs to dev class disk.

    tsm: SEADOG>QUERY STGPOOL BIGBACKPOOL
    Session established with server SEADOG: Linux/x86_64
    Server Version 5, Release 5, Level 4.0
    Server date/time: 01/06/10 17:16:39 Last access: 01/06/10 15:44:16

    Storage Device Estimated Pct Pct High Low Next Stora-
    Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
    Pct Pct
    ----------- ---------- ---------- ----- ----- ---- --- -----------
    BIGBACKPOOL DISK 31 G 3.1 3.1 20 5 BACKLTOTAP-
    E0

  10. #10
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    facing issue wih reclamtion any one can help out please

  11. #11
    Moderator mikeymac's Avatar
    Join Date
    Jun 2003
    Location
    Syracuse, NY
    Posts
    893
    Thanks
    8
    Thanked 12 Times in 12 Posts

    Default

    Is it possible that the reclamation process needs to load two tapes from the OFFSITE pool? Are any of the OFFSITE tapes still in your library?

  12. #12
    Moderator BBB's Avatar
    Join Date
    Feb 2007
    Location
    Brisbane, Australia
    Posts
    2,075
    Thanks
    0
    Thanked 5 Times in 5 Posts

    Default

    Are all the primary pool volumes online and available (q vol).

    What appears in the actlog when you run reclamation (post all output).

    Are all your copypool tapes in unmountable state? If a copypool tape is still in mountable tape, it may choose to try to mount that tape to read it rather than a primary tape.

  13. #13
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi,

    Yes I have checked all the tapes in Primary storage pool "backltotape0" they are in Access: Read/Write mode.


    Below is the error in actlog.

    01/05/10 18:01:38 ANR1040I Space reclamation started for volume 000109L3,
    storage pool OFFSITE-BACKUP (process number 87).
    (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:39 ANR1044I Removable volume 000079L3 is required for space
    reclamation. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:39 ANR1176I Moving data for collocation set 1 of 1 on volume
    000079L3. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1082E Space reclamation is ended for volume 000079L3.
    There is an insufficient number of mount points available
    for removable media. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1163W Offsite volume 000019L3 still contains files
    which could not be moved. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1163W Offsite volume 000024L3 still contains files
    which could not be moved. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1163W Offsite volume 000022L3 still contains files
    which could not be moved. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1163W Offsite volume 000048L3 still contains files
    which could not be moved. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR1163W Offsite volume 000109L3 still contains files
    which could not be moved. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR0985I Process 87 for SPACE RECLAMATION running in the
    BACKGROUND completed with completion state FAILURE at
    06:01:41 PM. (SESSION: 471, PROCESS: 87)
    01/05/10 18:01:41 ANR4936I Reclamation of storage pool OFFSITE-BACKUP has
    ended. Files reclaimed: 0, Bytes reclaimed: 0, Files
    reconstructed: 0, Unreadable files: 0. (SESSION: 471)
    01/05/10 18:01:55 ANR0407I Session 473 started for administrator RKONDA
    (Linux86) (Tcp/Ip seadog.mul.ie.ibm.com(12997)).
    (SESSION: 473)
    01/05/10 18:01:55 ANR2017I Administrator RKONDA issued command: QUERY ACTLOG
    begint=now-00:10 (SESSION: 473)
    01/05/10 18:04:03 ANR2017I Administrator RKONDA issued command: QUERY
    PROCESS (SESSION: 473)
    01/05/10 18:04:03 ANR0944E QUERY PROCESS: No active processes found.
    (SESSION: 473)
    01/05/10 18:04:03 ANR2017I Administrator RKONDA issued command: ROLLBACK


    I have inserted the tape 000079L3 in Libraray....but still facing the same issue as "There is an insufficient number of mount points available for removable media".

    I have checked in 000079L3 in both libraries ULT3581_0 and ULT3581_1 but I am getting same error.

    tsm: SEADOG>q drive
    Library Name Drive Name Device Type On-Line
    ------------ ------------ ----------- -------------------
    DLT_0 DRIVE2 4MM Yes
    ULT3581_0 DRIVE0 LTO Yes
    ULT3581_1 DRIVE1 LTO Yes


    tsm: SEADOG>q vol 000079L3
    Volume Name Storage Device Estimated Pct Volume
    Pool Name Class Name Capacity Util Status
    ------------------------ ----------- ---------- --------- ----- --------
    000079L3 COPYPOOL-B- LTOTAPE1 571.9 G 44.8 Full
    ACKUP


    tsm: SEADOG>q devclass ltotape1
    Device Device Storage Device Format Est/Max Mount
    Class Access Pool Type Capacity Limit
    Name Strategy Count (MB)
    --------- ---------- ------- --------- ------ -------- ------
    LTOTAPE1 Sequential 5 LTO ULTRI- 1
    UM3C
    tsm: SEADOG>q devclass ltotape0
    Device Device Storage Device Format Est/Max Mount
    Class Access Pool Type Capacity Limit
    Name Strategy Count (MB)
    --------- ---------- ------- --------- ------ -------- ------
    LTOTAPE0 Sequential 1 LTO ULTRI- 1
    UM3C


    Previously when I did reclamation on offsite-backup it did not ask for copypool-backup tape, it was using backltotape0 which is the pripmary STG.

    tsm: SEADOG>q stg
    Storage Device Estimated Pct Pct High Low Next Stora-
    Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
    Pct Pct
    ----------- ---------- ---------- ----- ----- ---- --- -----------
    ARCHIVEPOOL DISK 5.0 M 0.0 0.0 90 70 BACKLTOTAP-
    E0
    BACKLTOTAP- LTOTAPE0 5,713,665 0.2 0.3 90 70
    E0 G
    BACKLTOTAP- LTOTAPE1 7,628,617 0.0 0.0 90 70
    E1 G
    BACKUPPOOL DISK 10.0 M 0.0 0.0 90 70 BACKLTOTAP-
    E0
    BIGARCHPOOL DISK 31 G 66.7 66.7 90 70 BACKLTOTAP-
    E0
    BIGBACKPOOL DISK 31 G 6.3 6.3 20 5 BACKLTOTAP-
    E0
    COPYPOOL-A- LTOTAPE1 7,628,617 0.0
    RCH G
    COPYPOOL-B- LTOTAPE1 5,863,775 0.2
    ACKUP G
    OFFSITE-AR- LTOTAPE1 0.0 M 0.0
    CHIVE
    OFFSITE-BA- LTOTAPE1 6,832,517 0.2
    CKUP G
    SPACEMGPOOL DISK 0.0 M 0.0 0.0 90 70


    There is only one drive in each libraray.

    I have changed the mount limit value to drives and tried the relcamation but still getting the same error.

    Primary STG backltotape0 belongs to devclass LTOTAPE0 with one drive in it.

    Both copypool-backup and offsite-backup belong to devclass LTOTAPE1 and there is only one drive in it.

    Since there is only one drive for that LTOTAPE1 devclass its throwing error "There is an insufficient number of mount points available for removable media"

    Previously when I did reclamation on offsite-backup it did not ask for copypool-backup tape, it was using backltotape0 which is the primary STG.

    Could any one suggest why I am not able to run reclamation, please suggest me.

    Device Class Name: LTOTAPE0
    Device Access Strategy: Sequential
    Storage Pool Count: 1
    Device Type: LTO
    Format: ULTRIUM3C
    Est/Max Capacity (MB):
    Mount Limit: 1
    Mount Wait (min): 60
    Mount Retention (min): 2
    Label Prefix: ADSM
    Library: ULT3581_0
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    more... (<ENTER> to continue, 'C' to cancel)
    Drive Encryption: Allow
    Scaled Capacity:
    Last Update by (administrator): RKONDA
    Last Update Date/Time: 01/07/10 12:35:16
    Device Class Name: LTOTAPE1
    Device Access Strategy: Sequential
    Storage Pool Count: 5
    Device Type: LTO
    Format: ULTRIUM3C
    Est/Max Capacity (MB):
    Mount Limit: 1
    Mount Wait (min): 60
    Mount Retention (min): 2
    Label Prefix: ADSM
    Library: ULT3581_1
    Directory:
    Server Name:
    Retry Period:
    Retry Interval:
    Shared:
    High-level Address:
    Minimum Capacity:
    WORM: No
    Drive Encryption: Allow
    Scaled Capacity:
    Last Update by (administrator): RKONDA
    Last Update Date/Time: 01/07/10 12:35:25

    Thanks in Advance
    rkonda

  14. #14
    Moderator BBB's Avatar
    Join Date
    Feb 2007
    Location
    Brisbane, Australia
    Posts
    2,075
    Thanks
    0
    Thanked 5 Times in 5 Posts

    Default

    I have checked in 000079L3 in both libraries ULT3581_0 and ULT3581_1 but I am getting same error.
    Uhhh that could be part of the problem. Check the tape only into ONE library, the one that isn't the copypool... You should really only have all the tapes checked into only one tape library, have never seen them checked into two libraries before. Not even sure if its possible but you said you did it...

    Check with "q libvol * <volname>" where each tape is checked in and repost your results.

  15. #15
    Newcomer
    Join Date
    Jan 2010
    Posts
    21
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi,

    Below is the output

    tsm: SEADOG>q libvol * *
    Library Name Volume Name Status Owner Last Use Home Device
    Element Type
    ------------ ----------- ---------------- ---------- --------- ------- ------
    ULT3581_0 000002L3 Private Data 2
    ULT3581_0 000004L3 Private Data 5
    ULT3581_0 000012L3 Private Data 8
    ULT3581_0 000044L3 Private 6
    ULT3581_0 000045L3 Private Data 3
    ULT3581_0 000072L3 Private Data 4
    ULT3581_0 000083L3 Private Data 7
    ULT3581_0 CLNU64L1 Cleaner 1
    ULT3581_1 000020L3 Private SEADOG 5
    ULT3581_1 000030L3 Scratch 4
    ULT3581_1 000036L3 Private SEADOG Data 8
    ULT3581_1 000037L3 Private SEADOG 2
    ULT3581_1 000038L3 Private SEADOG Data 7
    ULT3581_1 000094L3 Private SEADOG Data 6
    ULT3581_1 000103L3 Private SEADOG Data 3
    ULT3581_1 CLNU64L1 Cleaner 1

    tsm: SEADOG>q vol 000079L3
    Volume Name Storage Device Estimated Pct Volume
    Pool Name Class Name Capacity Util Status
    ------------------------ ----------- ---------- --------- ----- --------
    000079L3 COPYPOOL-B- LTOTAPE1 571.9 G 44.8 Full
    ACKUP


    Could you please check and let me know how can I go head with reclamation.

Similar Threads

  1. Volume Reclamation Issue
    By vanberge in forum Tape / Media Library
    Replies: 3
    Last Post: 07-29-2009, 03:43 PM
  2. Backup issue after SAN issue
    By Archimedes in forum Backup / Archive Discussion
    Replies: 2
    Last Post: 07-24-2009, 05:49 AM
  3. TSM OR issue
    By venkattsm in forum TSM Installation, Upgrade and Configuration
    Replies: 3
    Last Post: 10-18-2008, 06:17 AM
  4. Reclamation issue
    By gerbera in forum TSM Server
    Replies: 6
    Last Post: 01-24-2008, 12:43 AM
  5. Space reclamation issue
    By mahe_l in forum Backup / Archive Discussion
    Replies: 2
    Last Post: 03-29-2007, 08:05 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •