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 Jan 24, 2016

AUDIT VOLUME command enhancement

One of the features of the current AUDIT VOLUME command is that while an audit process is active, clients cannot restore data from the specified volume or store new data to that volume. This can be a significant issue for audit volume processes that run for many hours or even days.

Auditing 'large' volumes can be a lengthy process. My suggested enhancement to the AUDIT VOLUME command is a QUICK=YES switch to prematurely stop auditing a volume once all the existing damaged files on the volume have been fixed by Tivoli Storage Manager.

For example, if Tivoli Storage Manager is only aware of a single damaged file on a volume (reported as 'damaged' in the CONTENTS table) then operationally it would make more sense to stop auditing as soon as Tivoli Storage Manager has fixed this single file. It's possible that new damaged files may be found if the audit of the volume was allowed to continue, but often the damaged file has only been detected because a restore of the file failed. Making the volume usable as quickly as possible to allow the restore to be completed is a higher priority than looking for other damaged files on the volume. Suitable informational messages recommending that a full audit be completed could accompany the use of this QUICK=YES switch.

My current workaround in the absence of this switch is to constantly run a query to determine the number of damaged files on a volume and to cancel the AUDIT VOLUME process once the number of damaged files reaches zero.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 30, 2019

    To just fix damaged files an onlydamaged=yes option would be even better.

    Use case: A 15 TB tape that has gotten files flagged as damaged 10 TB in due to lin_tape crash or some other sporadic error while reading.

    In this case I know that all files are OK, I just want to investigate the damaged files to get them back on track.