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.
This was delivered in Spectrum Protect 8.1.10.
Note that DB2 supports writing directly to S3 and Softlayer protocols.
Allowing TSM/SP to configure that would be the key here.
Azure support in DB2 is not available; though there is an RFE for that.
Ditto. Cloud and containers are basically a file class. We should be able to DEFINE DEVC DEVT=CLOUD.
From there, we should be able to set the container name (server_FOOBAR_DRM instead of a non-descript hex UID).
From there, we should be able to do PREPARE, BACKUP DEVC, BACKUP VOLHIST, and BACKUP DB.
The main issue there is including the access key, which needs to not be in cleartext. That precludes setting DRMPLANPREFIX and server options to URLs. Usually, an access key can be re-issued if lost, so it should not be super critical during DSMSERV RESTORE DB. We could just specify either on CLI, or in a text file.