Error Message

No error, as such, was observed - see above

As per e2739601, "vradmin repstatus" calculates Timestamp as the difference between the time stamp
of last data written on the SRL and the last data that was acknowledged from
the secondary.

Whenever any write is done on the primary , at the end of the asynchronous phase
of the update if the Rlink is up-to-date(connected or disconnected/paused), then
we mark the ri->pstate->last_ack_update_time as the timestamp of the update just
written.

This will ensure vradmin repstatus does not print a weird time stamp when no
data has been replicated across for a long time.

The change for this will be included via e2739601 in 5.1SP1RP3

Applies To

AIX 6.1

Storage Foundation SF5.1SP1RP1

In the example highlighted below, "vradmin repstatus" reported:
Data status: consistent, behind
Replication status: paused by user (primary paused)
Logging to: SRL (918989 Kbytes behind, 87% full)
Timestamp Information: behind by 0h 34m 34s

At the time, there was no active data. The timestamp information indicated that the "behind" time was 34 minutes, although it only took 2 minutes to get the rlink up-to-date