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.
PROTECT to the cloud is a long-term wishlist item, but confirmation was received that it is not planned for any release through 2019.
There may be other features on the board that may fulfill some use cases of this RFE.
OK, PROTECT to a remote CONTAINER pool works, but it cannot tier that data to a cloud pool.
Sorry for leaving a streak of misunderstanding here.
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 or file class would be be needed to really fix this.
An implementation of this I'd love to see would be:
REPLICATE NODE * TOSERVER=foobar
PROTECT STGPOOL TOSERVER=foobar
Getting to the cloud should be no problem now (8.1.3) though.
REPLICATE NODE can go to a cloud pool on the remote server.
PROTECT STGPOOL can go to a tiered pool which migrates to the cloud with no delay.
A fantastic RFE - I hope this gets through.
Would also like to see active data remain in a directory pool when replicating data to a cloud container pool. Currently data is temporarily stored in a directory pool till it is replicated to the cloud container pool, but will be nice to keep a cache of the active data instead of having to drag it back from the cloud which which will be both slow and expensive due to cloud providers charging for outgoing data.