IBM System Storage Ideas Portal
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.
Discussing with TSM L2, note that if you have damaged extents, that does not mark the objects damaged.
So, if a container is lost, then "REPL NODE * RECOVERDAMAGE=ONLY" does not repair any of the pool data.
Even if you use tiering, PROTECT STG to the second server stays in the local pool. It cannot migrate.
Basically, the only useful purpose for a cloud copy server is if the primary server dies.
There is no way to PROTECT STG nor BACKUP STG for a container pool other than a second full copy on tape, local disk, or second TSM server disk. It cannot go to a cloud pool.
A quasi-workaround would be to disable sessions, and reverse replication, then set back to normal.
Pools will self-heal if you replace the extents from a client, but some clients (TDP VMWare) fail to back up at all if their existing data has damaged extents.
This reiterates the need for a CLOUDCOPY pool type.
Just to clarify my last comment, PROTECT STGPOOL can only go to a REMOTE tiered pool, not a local tiered pool.
Being able to have a CLOUDCOPY backed by a local cloud or dir class would be be needed to really fix this.
Note that PROTECT STGPOOL can go to a tiered pool which migrates to the cloud with no delay, at least in 8.1.4.
This RFE should probably be re-tested to make sure it has not been delivered already.
Jacques' RFE is not the same thing. He is asking for a third copy with REPLICATE NODE.
This RFE is requesting PROTECT STG to be allowed with a target pool type of CLOUD.
Basically, we need to have POOLTYPE=COPY option for cloud pools.
That would solve other related problems too.
Duplicate RFE. Original one already has 32 votes and is in an "Uncommitted Candidate" status. Link to original RFE is:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=109500