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.
Yes, I did solve this problem by creating my own script that does the work of starting the backups and monitoring them and keeping and updating the queue of volumes to be backed up.
I understand if I'm the only one with this problem there won't be a solution by IBM for this problem.
That's exactly what I did. I created a script that uses the command "backup node $nodename $volume wait=no toc=yes" to backup all the nodes. The issue here is performance. If I issued all the backup commands one by one as a sequence with the option wait=yes I would not get through the backups in a reasonable amount of time. Therefore the script issues x backups of volumes in parallel and monitors the running backups if they have ended already. As soon as one of the backup processes has finished, the script issues another volume backup. This way, there is always x backups running in parallel. x is a configurable amount (currently set to 5).
This is exactly what the parameter vmmaxparallel in ISP4VE does... ;-)