1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Is there a way to delete TSM node or nodes from db2?

Discussion in 'TSM Operation' started by moon-buddy, Jan 24, 2018.

  1. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    For one reason or another, I cannot remove a node from within the TSM server.

    Is there a way (or, has someone done this) to remove (drop the node) the node from DB2? This means doing the node drop activity using DB2 tools.
     
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    The short answer is yes.

    The long answer is that it may not delete other references to the node in other tables and may end up with inconsistencies in the database. I'd recommend pursuing the problem with remove node instead.
     
  4. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I agree that 'remove node' would be the best option but I cannot figure out why TSM cannot delete the filespace for the node. Running a 'delete filespace' finishes with no errors but running a 'remove node' after (even after a day), the TSM server says inventory exist. The node has been decommissioned a long time ago.

    As you know, if inventory exist, removing the node is not possible.

    Do you know the procedure to do this from the DB2 side, i.e., delete the filespace and delete the node?
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    No I don't.

    Does that node once have dedup data?
    What does "QUERY OCCUPANCY {NODE} F=D" show?
     
  6. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    'q occupancy <node_name> f=d' is not a valid command (f=d part).

    Anyways, it shows the data - system state remaining:

    Code:
    Node Name      Type     Filespace      FSID     Storage         Number of        Physical         Logical
                            Name                    Pool Name            Files          Space           Space
                                                                                     Occupied        Occupied
                                                                                          (MB)            (MB)
    ----------     ----     ----------     ----     ----------     -----------     -----------     -----------
    NODE1          Bkup     NODE1    -        1     WINTEL         102,077,914      299,290.78      297,285.78
                             \SystemS-
                             tate\NUL-
                             L\System
                             State\Sy-
                             stemState
    
    For system state - this size is NOT normal. By the way, no dedup.
     
  7. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    So, no dedup data. I wanted to rule that out because the first node to do a backup will own the extents created. If a 2nd node does a backup and some extents are common to the 1st node, they are referenced. So when you delete the filespace for the 1st node, Q OCC still shows it, but as DELETED. That's because the node can't be deleted if it owns extents referenced by other nodes. This is NOT your case, so let's move on.

    I'd try to delete that filespace again. Don't need to target that one specifically, just: DEL FI NODE1 *
     
  8. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I ran multiple 'delete filespace <node> *' and the deletion process completes BUT the filespaces still remains. I even tried to be FSID specific for this remaining filespace but the same result.

    I went even further as to unload and reload the TSM DB to no avail.

    Really puzzled as this is happening to just this node.
     
  9. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
  10. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
  11. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Didn't think it applied, but as I said, it's a quick check so may as well rule it out.
     
  12. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Anyways, thanks -

    I may have to decommission this server as the DB is blotted and I believe this node is part of why it is.
     
  13. chad_small

    chad_small ADSM.ORG Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,253
    Likes Received:
    49
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    Have you tried deleting the objects directly using the

    delete object 0 <object_id>

    process like many have done for orphaned Oracle data?

    select 'del object 0', object_id from backups where node_name=<NODE_NAME>
     
  14. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Try to decommision the node in Spectrum Protect, before you decommision it, create a new domain that only has a default management class, and set the retention to 1 day. That way it should expire quick. Actually you could move to a new domain after decommissioning too.
     
  15. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I was thinking of doing this before I do Chad's suggestion - had done this before and worked well.

    Stay tuned.
     
  16. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Update:

    Changed retention for the node in question to 1 day, run expire inventory against the node and then delete filespace to be sure.

    Did a q filespace and node shows the FSID with ZERO capacity; and still cannot delete the node since inventory still exists!

    Dumbfounded by this!
     
  17. chad_small

    chad_small ADSM.ORG Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,253
    Likes Received:
    49
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    Did you delete the objects using the delete object command?
     
  18. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Are you using Spectrum Protect dedup? I believe not, I think you use DataDomain, but I have to ask to be sure.
     
  19. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,886
    Likes Received:
    367
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Tried the object delete and no, TSM dedup is not in use.
     
  20. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,712
    Likes Received:
    375
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    With rounding, it's possible there's a tiny bit of data and will show up as 0 if it's less than 0.05% used. Check query occupancy to see if the number of bytes and files is 0.
     
  21. Parul

    Parul Newcomer

    Joined:
    Aug 19, 2015
    Messages:
    2
    Likes Received:
    0
    Check activity log. It should mention, why cannot delete file space.
     

Share This Page