1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above 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 notice will disappear after you have made at least 3 posts.

Delete node data

Discussion in 'TSM Operation' started by moon-buddy, Apr 13, 2017.

  1. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,780
    Likes Received:
    352
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Does anyone know of a way to delete node data that sits on a storage pool? Data is SQL backup.

    Here is the scenario:

    I have a node that has data on two different storage pools. I want to delete data from one Storage pool. Waiting for retention to kick in is not an option.

    Does someone know of a direct way or a DB2 way to do this?
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,424
    Likes Received:
    343
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    If you can single them out in a select query, you could get the object ID and create a macro that does:
    delete obj 1234
    delete obj 5678
    etc...


    Or you could do a move nodedata from so that data is on specific volume(s), and do a delete volume discardata=yes for those volumes.
     
  4. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,780
    Likes Received:
    352
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    As it turned out, it would be simple - I dug deeper and realized that my backups are collocated by node. So it means that a volume is occupied by only one node. It is then a matter of deleting related volumes.

    However, if reclamation runs, it is possible that the volume from the older storage pool can be holding newer data. The likelihood of this happening is significant. Thus, OBJECT deletion should be the best option as mentioned by marclant.

    Comments?
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,424
    Likes Received:
    343
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Edited to remove destructive command as it's no longer needed.
     
  6. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,424
    Likes Received:
    343
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Reclamation doesn't move data across pools. Unless you meant migration
     
  7. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,780
    Likes Received:
    352
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Yep, migration. Reclamation does not move data between storage pools.
     

Share This Page