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.

Reclamation process problem!

Discussion in 'TSM Operation' started by shardron, May 6, 2009.

  1. shardron

    shardron New Member

    Joined:
    Nov 24, 2008
    Messages:
    3
    Likes Received:
    0
    I want to end a reclamation process. I loaded the "cancel pro " command, after that,stat of the process became PENDING.

    If anyone knows a command to cancel the reclamation process,plz tell me,thanks!

    :up:
     
  2.  
  3. shardron

    shardron New Member

    Joined:
    Nov 24, 2008
    Messages:
    3
    Likes Received:
    0
    Sorry, I think I should load command:

    update stg tapepool reclaim=100

    to solve the problem!
     
  4. JohanW

    JohanW Moderator

    Joined:
    Nov 12, 2006
    Messages:
    986
    Likes Received:
    14
    Occupation:
    sysadmin
    Location:
    Netherlands
    It'll end when it feels like it (when it finishes moving the current physical file. Which may be huge). Or restart the TSM Server service or process, that'll end it *now*.
     
  5. JohanW

    JohanW Moderator

    Joined:
    Nov 12, 2006
    Messages:
    986
    Likes Received:
    14
    Occupation:
    sysadmin
    Location:
    Netherlands
    update stg <stgpool> reclaim=100 will not stop a running reclaim process. It will cause no new processes to be started.
     
  6. mikeatkc

    mikeatkc Senior Member

    Joined:
    Apr 24, 2007
    Messages:
    450
    Likes Received:
    4
    Location:
    United States
    You can do a "cancel proc #" to cancel the process. However, as Johan mentioned, reclamation will ends when the current file/action is completed.
     
  7. kinscoe

    kinscoe New Member

    Joined:
    Jun 12, 2008
    Messages:
    4
    Likes Received:
    0
    Location:
    Eastern NC
    I had the same issue the other day. As it turned out it was in the middle of reclaiming a 649 GB imagebackup file.
     
: reclamation

Share This Page