This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Decommission node is now available via the IBM Spectrum Protect / Tivoli Storage Manager Operations Center v7.1.3.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
An add to this RFE. Decom should also be per filespace.
I would like to add a new column to the table "NODES"
New column: "LifeCycle" with option "Under Implementation", "Testing", "Production", "Quarantine", "End of Deployment" and "Scrapped"
And
reg n ... lifecycle='production'
upd n .... lifecycle='EOD'
I have been renaming ny nodes to TERM_YYMMDD_nodename. Then I have a script that runs weekly that finds those nodes that has passed the date and deletes the filespaces and then the node.
Great Idea. But remember to make the revserse command, if the node should be back in service.
It would be nice ig the decommisionen node could keep its schedule associations, in case the node should need them again.
Brilliant idea and very practical.
Would be good to have a scheduled process window for the node(s) purge as well so that all expired nodes can be purged in a window away from expiration and other housekeeping tasks,
Awesome idea! I've been putting my decommissioned nodes into a separate storage pool as a workaround.
A great idea. See RFE 20847 for additional suggestions
We have received a workaround example which worked ok.
example could be found here:
http://www.repostor.com/joomla/index.php?option=com_content&view=article&id=151%3Ainactivate-filespace-tsm-server-6&catid=36%3Arepostorbestpractice&Itemid=96&lang=sv
I call this example: "inactivatefs"
Thank you for submitting this enhancement request, we plan to provide this functionality in a future release of TSM.