Re: replication status

[Chris Whisonant <Chris.Whisonant@xxxxxxxxxxxxx>]

Sort of - see below

[009236:03734:00008-00003416] > show stat replica 
 
[009236:03734:00008-00003416]   Replica.Cluster.Docs.Added = 3196 
[009236:03734:00008-00003416]   Replica.Cluster.Docs.Deleted = 2103 
[009236:03734:00008-00003416]   Replica.Cluster.Docs.Updated = 827 
[009236:03734:00008-00003416]   Replica.Cluster.Files.Local = 1281 
[009236:03734:00008-00003416]   Replica.Cluster.Files.Remote = 1295 
[009236:03734:00008-00003416]   Replica.Cluster.Retry.Waiting = 0 
[009236:03734:00008-00003416]   Replica.Cluster.SecondsOnQueue = 0 
[009236:03734:00008-00003416]   Replica.Cluster.SecondsOnQueue.Avg = 6 
[009236:03734:00008-00003416]   Replica.Cluster.SecondsOnQueue.Max = 15 
[009236:03734:00008-00003416]   Replica.Cluster.Servers = 1  
[009236:03734:00008-00003416]   Replica.Cluster.SessionBytes.In = 3245574  

[009236:03734:00008-00003416]   Replica.Cluster.SessionBytes.Out = 
173986070
[009236:03734:00008-00003416]   Replica.Cluster.Successful = 5378  
[009236:03734:00008-00003416]   Replica.Cluster.WorkQueueDepth = 0  
[009236:03734:00008-00003416]   Replica.Cluster.WorkQueueDepth.Avg = 9  
[009236:03734:00008-00003416]   Replica.Cluster.WorkQueueDepth.Max = 72  
[009236:03734:00008-00003416]   Replica.Docs.Added = 3280  
[009236:03734:00008-00003416]   Replica.Docs.Deleted = 2356  
[009236:03734:00008-00003416]   Replica.Docs.Updated = 1017  
[009236:03734:00008-00003416]   Replica.Failed = 50  
[009236:03734:00008-00003416]   Replica.Successful = 11298  
[009236:03734:00008-00003416]   21 statistics found  

Chris Whisonant
Senior Mid-Range Systems Administrator
Comporium
803-326-7270
IBM Certified Specialist -- eServer i5 iSeries Domino Technical Solutions 
V5R3
IBM eServer Certified Systems Expert - iSeries Technical Solutions V5R2
IBM Certified Advanced System Administrator - Lotus Notes and Domino 
6/6.5/7
IBM Certified Associate Developer - Lotus Notes and Domino 6/6.5 



From:
rob@xxxxxxxxx
To:
domino400@xxxxxxxxxxxx
Date:
04/27/2007 11:15 AM
Subject:
replication status


Scenario:  You were down for a day.  CLREPL and SMD* jobs are chomping 
away.
Question:  Is there any way to check the status to see how much longer 
until they are caught up?  Or how many transactions are behind?

With my i5/OS HA software I can see:
- How many journal entries are on the remote versus local
- How many journal entries on the backup system have been read by the HA 
software
- How many journal entries have been read, but are waiting to be posted.
I was hoping to see something like this for cluster monitoring.

Rob Berendt