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 Under review
Created by Guest
Created on Dec 7, 2023

Extension of the Table "Replicationview" by the columns batchesQ and batchesD

Hello, the command "show replication" shows the number of "batchesQ" and "batchesD".
Is it planned to implement the number of "batchesQ" and "batchesD" in the table REPLICATIONVIEW?
Currently I can't find any columns in this table regarding this.


Entry 2043
server: VIUTSMSP10
priority: 8 state: Disk in progress
nodeName: KLUDB901_PRODRAC fsName: /ORBIS_KHV
nodeId: 45 fsId: 1 replMode: 0
copyType: Backup lowIdx: 0 highIdx: 0
purge: No rc: 0 activeOnly: No
numBatches: 507 hasTape: Yes serverId: 1
tgtNodeId: 41 tgtFsId: 1 updCount: 0
deletePriority: High Priority tcrEnabled: No
Backup Stats, statsP at 130b8f850
file stats:
Current: 5771 To repl: 696 Repld: 672
Repl errT: 0 Repl errS: 0
To upd: 0 Updated: 0 Upd err: 0
To del: 0 Deleted: 0 Del err: 0
indentify time: 1069 seconds
byte stats:
To repl: 11605854198792 Repld: 11487937883888 Xferred: 31720528636
Repl errT: 0 Repl errS: 0
Xfer time: 262504 seconds
snapshot stats:
To repl: 0 Repld: 0
Repl errT: 0 Repl errS: 0
To del: 0 Deleted: 0 Del err: 0
indentify time: 1069 seconds
byte stats:
To repl: 11605854198792 Repld: 11487937883888 Xferred: 31720528636
Repl errT: 0 Repl errS: 0
Xfer time: 262504 seconds
batchesQ: 507 batchesD: 503 ------------------------------------------> can be a good overview how many batches must be transferred to finish the replication for a specific node.

Regards,

Günther

Idea priority Medium
  • Admin
    Juan Carlos Jimenez Fuentes
    Reply
    |
    Jan 11, 2024

    Hello, can you give us more details on the problems you are trying to solve? How are you using batchesQ and batchesD?

    1 reply