1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

Offsite Storage Pool makes volumes "EMPTY" But does not call them back for scratch

Discussion in 'Tape / Media Library' started by mystblade, Jan 3, 2008.

  1. mystblade

    mystblade New Member

    Joined:
    Mar 22, 2005
    Messages:
    5
    Likes Received:
    0
    Hello -

    I have had this problem ever since I restored the database 1 month ago. It used to work just fine but now that when volumes are reclaimed from our offsite storage pools or expired, the voumes turn to a state of "EMPTY" and I have to manually do the command "Move Media Volume = STGPool= montablenotinlib command to put them back into the scratch pool from our offsite location.

    When it was automatic it would put it in the VaultRetrieve Status and not just Empty so when we run out DR process we get no VaultRetrieve volumes to pull back.

    The Reuse delay paremeter is set to 0 which to my understanding, makes them ready for use as soon as they are emptied.

    The Max Scratch Parameter is set to 100 and we currently only have 10 scratch volumes.

    Any help is greatly appricated, I have been scratching my head trying to figure out why it wont do this process automaticlly any more

    Thanks
     
  2.  
  3. chad_small

    chad_small Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,197
    Likes Received:
    43
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    When you restored the DB did you perform an audit every storage pool? Have you tried re-defining the DRM settings? Inconsistencies can arrise when you restore the DB to a point in time and the storage pools have not been audited. That coulde be what is causing the problem. Some of those tapes offsite probably don't register to the DB that they were in use by the copy pool or might show an incorrect data amount.
     

Share This Page