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.
Sorry, I did not get notified of this "more info" request. I just looked here again because of another idea ...
And it's been a while ago. So let me recapitulate. The customer wanted to use the S3 agent for backup of a HashiCorp vault. If I remember correctly, then the S3 implementation of IBM into the SP server did not include versioning of objects. E.g. if an S3 client wrote an object (file) with a name that already existed, then the existing object would simply be overwritten. But the S3 API has functionality to not overwrite but create a new version in such a case. And it would allow the S3 client to access not only the current but also older versions. That's about the same what the normal SP B/A agent already uses so the SP server does support this since ages - we all know of active and inactive versions and their expiration by copy group definition. So why does the S3 object agent not use this SP server capability to implement S3 versioning?
A customer implemented a backup solution for Postgres and MongoDB databases using this as the S3 repository. Now they also want to implement such for HashiCorp Vault. That always writes (or could write) the same object name so classic versioning with expiration of older versions like in plain TSM would be desirable. And original AWS S3 API provides functionality for such a solution.
Can you please describe the use case further? Which workloads and how do you plan to use it? What are the current space challenges?