Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Created by Guest
Created on Jun 29, 2015

Exclude VMs based on VM size/.vmdk size with dsm.opt/cloptset exclusion

With the explosion of virtual machines taking over our datacenters, using TSM for Virtual Environments is crucial to successfully protecting the data in our IT organizations. It is obvious that there is no "one size fits all" tool for protecting these virtual environments as the workload/size/configuration is vastly different. Requirements and dependecies are often unique, many of these stem from internal decisions and not software/hardware limitations.

The need to easily identify the large "monster" VMs and subsequently exclude the entire VM based on total VM size or exclude individual .vmdks based on individual .vmdk size. Having a message posted to the TSM server activity log and the dsmsched/dsmerror log on the datamover would need to be in place as well to allow effective monitoring/auditing of the VM backup environment.

Idea priority Urgent