• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • 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.

  • 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.

Problem with NDMP Node Deletation

#1
Hello,

I have a problem with the NDMP-node deletion.

Error ANR2152E REMOVE NODE : Inventory references still exist for node xxx.
ANS8001I Return Code 13.
There is no filespaces. I have deleted all schedulers, rules and datamovers for this node.

When I do "q node xxx f=d", there is no information.
When i do "select * from nodes where node_name ='xxx'" all information for this node is there.
So how can i solve this Problem?
 

moon-buddy

ADSM.ORG Moderator
#12
The odd thing here is that you has deleted all the filespaces related to that NAS node. On removing the node, you get "inventory still exists" errors but 'q filespace" tells you that nothing is there.

I forgot to ask what is your BA client and Storage agent version.

I have not encountered this issue with NAS nodes and all deletion of NAS nodes goes smoothly. I am beginning to believe you may have hit a bug or your TSM DB is messed up.

Have you run 'expire inventory' lately? I don't believe this is related and a long shot. Give it a try and see if this puts the system in order.
 
#13
The odd thing here is that you has deleted all the filespaces related to that NAS node. On removing the node, you get "inventory still exists" errors but 'q filespace" tells you that nothing is there.

I forgot to ask what is your BA client and Storage agent version.

I have not encountered this issue with NAS nodes and all deletion of NAS nodes goes smoothly. I am beginning to believe you may have hit a bug or your TSM DB is messed up.

Have you run 'expire inventory' lately? I don't believe this is related and a long shot. Give it a try and see if this puts the system in order.
Command Line Administrative Interface - Version 6, Release 2, Level 4.0
I have done expire inventory, but it did not help me, I have stll the same problem with nas nodes
 
Last edited:

Bobo-Da-Hobo

Active Newcomer
#17
Sorry, saw your post about datamovers after i sent this.

Hi,

I recall having this issue myself. As far as can remember the NAS node cannot be removed until you have deleted the associated datamovers. There may also be a requirement to remove any virtual mappings.

good luck!
 
Last edited:

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 17 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 53 60.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.5%
  • Other (please comement)

    Votes: 7 8.0%

Forum statistics

Threads
31,471
Messages
134,133
Members
21,569
Latest member
srinathkodela
Top