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.
See this idea on ideas.ibm.com
Hi Mitul,
I have the answer now for the difference between client restore from cloud vs replication from cloud
1: the normal restore from the cloud was making use of the chunk cache and
async read. Those tools can in some cases make the restore from cloud very efficient, The "cache : yes" from your last resource, shows the chunks are in cache, as a result, the restore doesn't need to go to the cloud at all (this is why I don't see the cloud read from cloud for the restore thread ).
However, not all the chunks are in cloud, if you are restoring chunks are not in cloud ( cache: NO), the restore will have to go to the cloud, and the performance would be a lot slower than what we saw in this example.
2: The replication path does not use that chunk cache, or async read, so it has to read every chunk from the cloud every time, so it will consistently have that slower performance.
If you are not satisfied with our current replication design. you can certainly open a RFE for this subject:
Link to RFE
https://www.ibm.com/developerworks/rfe/?BRAND_ID=90
Choose: brand/ product: Servers and system software
Prodct: spectrum protect family
Regard,
Hellen Jin
Show less
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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.