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 Future consideration
Created by Guest
Created on Oct 6, 2021

CSM triggered backup of logs -feature add

CSM should trigger automatic backup of logs to files
in case of a critical event related to replication occurs. Reason to request this feature >
CSM logs are getting overwritten in a very short period of time that critical events disappear from log and it makes RCA impossible.

Idea priority High
  • Guest
    Reply
    |
    Oct 7, 2021

    So there are actually some events that will trigger automatic log package creation. A failed GM recover command, failed scheduled task or a failed backup are a few examples. The issue with this request is defining exactly what events should warrant an automatic log package. Too "many" log package triggered could affect performance. And each creation of a log package can take up disk space. On and CSM HMC installation, disk space isn't an issue because we will automatically only keep 5 log packages. But on a standalone server, there is nothing that roles older log packages and running out of disk space could cause issues with CSM and other products.

    So, I would be greatly interested if you could provide a list of events that you think you'd want to see automatic log packages created for.