Tape Storage

 View Only
Expand all | Collapse all

Scratch tape is not creating

  • 1.  Scratch tape is not creating

    Posted Wed November 27, 2019 03:27 PM
    Hi All,

    We have one library manager and Library client both 5.5 I have a space crunch I tried all the way but scratch is not creating tried running reclamation and expiration manually as well here is the details of current situation.

    I ran this :-

    SELECT volume_name,devclass_name,stgpool_name,pct_reclaim,pct_utilized,status,access FROM volumes order by pct_reclaim

    i have 100 of tapes which is showing to be reclaimable but no tapes are converting on scratch as of now.

    ------------------------------
    Prem Singh

    ------------------------------


  • 2.  RE: Scratch tape is not creating

    Posted Thu November 28, 2019 04:11 AM
    Hi Prem,
    are there any scratch tapes in the storage pool left? If not the reclaim will not run.
    On which value is the reclamation threshold set for this storage pool?

    Some output of your commands would be helpful.... e.g from your select commnd and a q stgp of the affected storage pool.

    Best regards,
    Jochen

    ------------------------------
    Jochen Meixner
    Principal Consultant Storage & Backup Solutions
    CONET Services GmbH
    Duesseldorf, Germany
    ------------------------------

    Original Message


  • 3.  RE: Scratch tape is not creating

    Posted Thu November 28, 2019 06:32 AM
    Hi Jochen,

    Thanks for the response on this environment there is no offsiting we don't purchase tapes because of legacy I will post the result in the night once I will be in office there is one pool called fs_tape it has more than 300 tapes which is full and reclaim threshold on stgpool is 100% and we have admin jobs for reclaim on 60%


    Thanks 
    Prem 




    Original Message


  • 4.  RE: Scratch tape is not creating

    Posted Thu November 28, 2019 03:37 PM
    Hi,
    Please find the output.

    q stg FS_TAPE f=d

    Storage Pool Name: FS_TAPE
    Storage Pool Type: Primary
    Device Class Name: LTOCLASS
    Estimated Capacity: 13,785,469 G
    Space Trigger Util:
    Pct Util: 10.8
    Pct Migr: 13.4
    Pct Logical: 100.0
    High Mig Pct: 90
    Low Mig Pct: 70
    Migration Delay: 0
    Migration Continue: Yes
    Migration Processes: 1
    Reclamation Processes: 2
    Next Storage Pool:
    Reclaim Storage Pool:
    Maximum Size Threshold: No Limit
    Access: Read/Write
    Description:
    Overflow Location:
    Cache Migrated Files?:
    Collocate?: No
    Reclamation Threshold: 60
    Offsite Reclamation Limit:
    Maximum Scratch Volumes Allowed: 9,999
    Number of Scratch Volumes Used: 1,341
    Delay Period for Volume Reuse: 3 Day(s)
    Migration in Progress?: No
    Amount Migrated (MB): 0.00
    Elapsed Migration Time (seconds): 0
    Reclamation in Progress?: No
    Last Update by (administrator): test
    Last Update Date/Time: 11/28/19 15:29:09
    Storage Pool Data Format: Native
    Copy Storage Pool(s):
    Active Data Pool(s):
    Continue Copy on Error?: Yes
    CRC Data: No
    Reclamation Type: Threshold
    Overwrite Data when Deleted:
    Deduplicate Data?: No
    Processes For Identifying Duplicates:
    Duplicate Data Not Stored:
    Auto-copy Mode: Client
    Contains Data Deduplicated by Client?: No

    and sample of few lines after select execution.


    VOLUME_NAME: C00301
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 46.7
    PCT_UTILIZED: 53.3
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00336
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 46.9
    PCT_UTILIZED: 53.1
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00220
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.0
    more... (<ENTER> to continue, 'C' to cancel)

    PCT_UTILIZED: 53.1
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: C00361
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.0
    PCT_UTILIZED: 53.0
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: NC0954
    DEVCLASS_NAME: COPYDUAL
    STGPOOL_NAME: COPYDUAL_TAPE
    PCT_RECLAIM: 47.0
    PCT_UTILIZED: 53.0
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: Z00188
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: ARCH_MONTHLY_TAPE
    PCT_RECLAIM: 47.0
    PCT_UTILIZED: 53.3
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: C00173
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.1
    PCT_UTILIZED: 52.9
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: C00265
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.1
    PCT_UTILIZED: 53.0
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: NP0038
    DEVCLASS_NAME: LTO5C
    STGPOOL_NAME: ARCH_DAILY_LTO5
    PCT_RECLAIM: 47.1
    PCT_UTILIZED: 2.8
    STATUS: FILLING
    ACCESS: READONLY

    VOLUME_NAME: A00137
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.2
    PCT_UTILIZED: 52.8
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: C00126
    more... (<ENTER> to continue, 'C' to cancel)

    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.2
    PCT_UTILIZED: 52.8
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: NC0155
    DEVCLASS_NAME: COPYDUAL
    STGPOOL_NAME: COPYDUAL_TAPE
    PCT_RECLAIM: 47.2
    PCT_UTILIZED: 52.9
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00120
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.3
    PCT_UTILIZED: 52.7
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00175
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.3
    PCT_UTILIZED: 52.7
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00197
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.3
    PCT_UTILIZED: 52.7
    STATUS: FULL
    ACCESS: UNAVAILABLE

    VOLUME_NAME: A00115
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.5
    PCT_UTILIZED: 52.5
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: A00471
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.5
    PCT_UTILIZED: 52.5
    STATUS: FULL
    ACCESS: READWRITE

    VOLUME_NAME: C00140
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.5
    PCT_UTILIZED: 52.7
    STATUS: FULL
    more... (<ENTER> to continue, 'C' to cancel)

    ACCESS: READWRITE

    VOLUME_NAME: Z00020
    DEVCLASS_NAME: LTOCLASS
    STGPOOL_NAME: FS_TAPE
    PCT_RECLAIM: 47.5
    PCT_UTILIZED: 52.5
    STATUS: FULL
    ACCESS: READWRITE

    ------------------------------
    Prem Singh
    TSM Admin
    IBM
    8527337214
    ------------------------------

    Original Message


  • 5.  RE: Scratch tape is not creating

    Posted Thu November 28, 2019 04:06 PM
    Hi Prem,
    ah, ok....

    The reclamation threshold for your pool is 60. This means a volume is reclaimed if there is 60% or more reclaimable space on it.
    In the excerpt of the select statement output are between 46,7 and 47,5% reclaimable space on the volumes.

    Please try an reclamation threshold of 45.
    Then the volumes should be reclaimed.

    Best regards,
    Jochen

    ------------------------------
    Jochen Meixner
    Principal Consultant Storage & Backup Solutions
    CONET Services GmbH
    Duesseldorf, Germany
    ------------------------------

    Original Message


  • 6.  RE: Scratch tape is not creating

    Posted Fri November 29, 2019 12:58 PM
    Hi,

    I tried on 40% as well but no luck however my TSM server is crashing all of a sudden, i have started another post for that.

    ------------------------------
    Prem Singh
    TSM Admin
    IBM
    8527337214
    ------------------------------

    Original Message


  • 7.  RE: Scratch tape is not creating

    Posted Sun December 01, 2019 01:07 PM

    Prem,

     

    It looks like your tape are not even 60% utilized which would mean reclamation would not run. Either you have to set reclamation very low or do some 'move data' commands on tape that might fit together. 

     

    When you query volumes in a stgpool, they will show how much they are utilized.  If you see any that say 'empty' you could delete them and they will be scratch.  If reclamation runs for a long time, it will leave the tapes in empty status until the reclamation job completes.  If you need them immediately, you could either delete them manually or cancel the reclamation job and start it over.  As the job finishes, it release all of the empty tapes.

     

    Q vol stgp=xxxx

     

    If you show some tapes in the pool as only partially full and in filling status, you could do the 'move' data command. This will only move data onto another volume within the same stgpool. It helps to consolidate the tapes though and will free up some tapes.

     

    Move data volume_name

     

    This is another concern regarding your stgpool:  Delay Period for Volume Reuse: 3 Day(s)
    Everyone has different reasons for using this and it may be of value in not wanting your tapes used again immediately after being scratched.  I have never found value in this myself and have in too many situations with small tape libraries so I set this to 0.  If you have a large library and lots of tapes and space for tapes, you can get by with having a delay.  If you have a small library and are cramped for space, you are just creating a delay for tapes to be reused again.  I would be curious how many tapes are in your library that are empty but have not met this 3 day criteria.  You should be able to see this by doing 'q vol stgp=*  status=empty'

     

    I hope these tips help some.

     

     

     

    Brenda Collins,

    Sr. Principal Systems Admin | Technical Operations Team

    Medtronic, Inc. | MVC63 | 8200 Coral Sea Street NE | Mounds View, MN 55112

    763.505.6057

    Brenda.s.collins@medtronic.com|

    medtronic.com  |  Facebook  |  LinkedIn  |  Twitter  |  YouTube

    LET'S TAKE HEALTHCARE
    FURTHER, TOGETHER

    Spectrum+Protect+V8_1

     

    [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com



    Original Message


  • 8.  RE: Scratch tape is not creating

    Posted Mon December 02, 2019 06:30 PM
    Hi Prem,
    your server version is rather old, end-of-life and out-of-support.

    Please check for empty volumes and delete them as @Brenda Collins mentioned.
    If there are no empty volumes, look for nearly empty volumes and do a move data on them to empty them.

    Could you please post the output of the following command?
    query volume C00301 f=d
    Perhaps the volumes are not set to scratch automatically....

    Best regards,
    Jochen
    ​

    ------------------------------
    Jochen Meixner
    Principal Consultant Storage & Backup Solutions
    CONET Services GmbH
    Duesseldorf, Germany
    ------------------------------

    Original Message


  • 9.  RE: Scratch tape is not creating

    Posted Tue December 03, 2019 02:01 PM
    Hi Jochen,

    Please find the output.

                  Volume Name: C00301
                 Storage Pool Name: FS_TAPE
                 Device Class Name: LTOCLASS
                Estimated Capacity: 1.0 T
           Scaled Capacity Applied:
                          Pct Util: 53.3
                     Volume Status: Full
                            Access: Read/Write
            Pct. Reclaimable Space: 46.7
                   Scratch Volume?: Yes
                   In Error State?: No
          Number of Writable Sides: 1
           Number of Times Mounted: 2
                 Write Pass Number: 1
         Approx. Date Last Written: 09/28/18   05:54:13
            Approx. Date Last Read: 07/21/19   01:08:18
               Date Became Pending:
            Number of Write Errors: 0
             Number of Read Errors: 0
                   Volume Location:
    Volume is MVS Lanfree Capable : No
    Last Update by (administrator):
             Last Update Date/Time: 09/28/18   02:07:16
              Begin Reclaim Period:
                End Reclaim Period:
      Drive Encryption Key Manager: None
           Logical Block Protected: No
    --
    Regards
    Prem 



    Original Message


  • 10.  RE: Scratch tape is not creating

    Posted Tue December 03, 2019 02:04 PM
    Hi Brenda,

    Good to hear from you after long time, thank you very much for the details explanation.

    empty tapes is only one.

    q vol stgp=*  status=empty

    Volume Name                  Storage         Device         Estimated       Pct      Volume
                                 Pool Name       Class Name      Capacity      Util      Status
    ------------------------     -----------     ----------     ---------     -----     --------
    A00022                       ARCH_MONTH-     LTOCLASS           0.0 M       0.0      Empty
                                  LY_TAPE

    --
    Regards
    Prem Singh Bathyal
    Contact- 8527337214



    Original Message


  • 11.  RE: Scratch tape is not creating

    Posted Tue December 03, 2019 07:13 PM
    Hi Prem,
    then delete the volume  A00022.

    Do you have some other scratch volumes in your library?
    select volume_name from libvolumes where status='Scratch'

    Did your storage pool perhaps reach the maximum count of allowed volumes?
    q stgpool <poolname> f=d
    Look for this two entries:
    Maximum Scratch Volumes Allowed: xxxx
    Number of Scratch Volumes Used: yyyy

    If there are scratch volumes and the pool is not "full", then try the reclamation once again.
    With a reclamation threshold of 45 there should be a lot of volumes be eligible for reclamation.
    So be careful and start with 50 and decrease slowly... So there should be less volumes to process.

    Best regards,
    Jochen



    ------------------------------
    Jochen Meixner
    Principal Consultant Storage & Backup Solutions
    CONET Services GmbH
    Duesseldorf, Germany
    ------------------------------

    Original Message


  • 12.  RE: Scratch tape is not creating

    Posted Thu December 05, 2019 06:12 AM
    Hi Jochen,

    I have tried all these steps already still scratch can be used on stgpool, deleted that volume as well and ran reclamation on 50, 45 and 40 as well but no result and another glitch which I found is on the library on 2 different frame one same label is reflecting I have requested local team to verify the barcode on both frames earlier so many duplicate are showing after running inventory from library only one is still exists.

    Thanks
    Prem 



    Original Message