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.
We have the same problem.
We generate our deduplication statistics daily, in order to observe depuplication trends and to be able to bill our customers for data volumes.
We also have the problem that our VMs that are backed up with TDP for VE (VMs ~1000) are grouped as filespaces in single node per VMWare cluster on the SP server.
The command "generate dedupstats" supports the option (MAXProcess) only on node level and not on filespaces level. This gives us very long runtimes, because only a single process is processing the VM node, which contains 1000 VMs as filespaces.
We need the support of the command "generate dedupstats", with the "MAXPROcess option" on the filespace-level!
If you set a rule to run generate dedupstats on all nodes, then it uses one process per node. It will process all of the other nodes, and drop down to a single process while it processes 1700 VMs. That process can run for days or weeks.
If you are suggesting that we create multiple rules which split the list of VMs individually, then I would say that is patently a horrible idea and exactly the thing I am asking for SP to not require.
If you are saying that the single process has multiple threads behind it, then why does it run multiple processes initially, and how would the thread count be adjustable? Because we can process thousands of filespaces in a few days when they are run as multiple processes, but it takes weeks to do the same when all of the filespaces belong to the same node.
We need a little more information: 1. The GEN DEDUPSTATS already allows for node/filespace which should allow for VM's. What's the issue here? 2. How frequently are you running this and why so frequently?