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 Oct 18, 2018

Spectrum Protect - update LASTACC_TIME when a target node is replicated to

Hi,

In Spectrum Protect, when a node in a replicated pair is replicated to (when it is the target) the LASTACC_TIME does not update.

We often use the LASTACC_TIME to determine if a node is still in use, if the LASTACC_TIME is over X days then we decom the node.

Can the LASTACC_TIME be set to update when a node is replicated to.

Or can there be a new node field that indicates when the node was replicated to, so the same as the filespace replication fields, but one for the overall node to indicate that it has had replication run against it (ie one or more filespaces replicated causes a node replication field to be updated).

Regards,
Scott

Idea priority Medium
  • Guest
    Reply
    |
    Nov 7, 2018

    IBM has evaluated the request, and has determined that it can not be implemented at this time or does not align with the current multi-year strategy. This request may be resubmitted for consideration after 18 months from the date of submission. The request submitter will automatically be notified by email when the request qualifies for reconsideration and resubmission.