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 Apr 24, 2013

Documentation update regarding Deduplication enabled Storage Pools using FILE Device Class type

Documentation update referencing the importance of proper storage pool "DATAFormat" type for DEDUPLICATION enabled SEQUENTIAL ACCESS Storage Pools of FILE Device Class.

As the user defines Sequential Access Storage Pool of FILE Device Class type the default DATAFormat of "Native" is NOT appropriate for storing deduplicated backup data.

Suggesting: to update the documents "IBM Tivoli Storage Manager Version 6.4 and Version 6.3 Optimizing Performance" - GC23-9788-04, "Effective Planning and use of TSM V6 Deduplication" and the "TSM Administator Guide".

The update should contain the note and the best practice recommendation to 'Define Sequential Access Storage Pool of FILE Device Class Type for use with TSM deduplication to be of DATAFormat=NONblock"

If using the default DATAFormat=NATive will result in waste of disk space allocated by the volume and reporting to be full when less than expected amount of data is stored.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |
    Jul 23, 2014

    Thank you for submitting this request. We understand what you are seeking however we will not be implementing an update to the documentation as suggested. We do have a large customer base where such a documentation change would not be beneficial, independent of deduplication. Please note the existing storage pool help documentation does provide some explanation as to when the nonblock dataformat can provide efficiency:

    NONblock
    Specifies the data format is the native Tivoli Storage Manager server format and does not include block headers.
    Important: The default minimum block size on a volume associated with a FILE device class is 256 KB, regardless how much data is being written to the volume. For certain tasks (for example, using content-management products, using the DIRMC client option to store directory information, or migrating very small files using Tivoli Storage Manager for Space Management or Tivoli Storage Manager HSM for Windows), you can minimize wasted space on storage volumes by specifying the NONBLOCK data format. In most situations, however, the NATIVE format is preferred.