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 Dec 27, 2011

TSM copy group parameters serialization and changedretries not honored with file is locked for read

When a file is being written to, TSM has the ability in some cases to do a fuzzy backup (serialization=dynamic). However there are exceptions if a file is locked for reading by the OS. Then TSM obviously can not get to it which is fine, but.... the behavior after is in question. In my use case below, I observed it retrying 4 times. This is with serialization set to dynamic, and later with changedretries set to a number lower than 4.. It still retries 4 times. My suspicion is that if the process determines the file is locked for reading, it does not observe the intended management class settings, and uses the default class (again- last sentence is speculation based on observation, not code tracing). I opened a PMR with support that shows some log details.

Idea priority Low
  • 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