
HP NonStop Shadowbase Command Definitions
Consumer Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
151
When a pulse is acknowledged (i.e., AUDMON receives a pulse
acknowledgment message), if the difference between the target I/O
completion time and the time the pulse was created/inserted into the
source pulse file is greater than PULSEMAXREPSONSE, AUDMON will
output an EMS message to identify that the pulse is “out of band” (i.e.,i.e.,
replication latency is not within PULSEMAXRESPONSE). Subsequent
pulses that also come back “out of band” will also be output to EMS,
subject to the PULSEWARNRATE interval.
Note: That if a completed pulse is back “in band” (within the
PULSEMAXRESPONSE time) and the prior pulse was “out of
band”, an EMS message will be reported indicating that pulsing on
this replication thread is now “in band”. If HP Shadowbase
replication is significantly behind, it might be desirable to alter
PULSEMAXRESPONSE to a higher value for a period of time to
disable the “out of band” messages from being reported to EMS.
This parameter can be altered at any time.
Note: That “true” replication latency monitoring via the
PULSEMAXRESPONSE expects the source and target system
clocks to be synchronized (either with each other or with GMT).
However, this is often not the case. The NonStop and HP
Shadowbase Other Servers support similar parameters to correct
for the situation where the clocks are not synchronized. On the
NonStop side these parameters are PULSECLOCKADJ and
PULSESVRCLOCKADJ. These parameters can be automatically
controlled through the use of the PULSEAUTOADJ parameter.
PULSERATE <seconds>
Initial Changed
Version Version Values Default Minimum Maximum Alter
3.990 0 (disabled) 0 1209600 Yes
Client Server Extended Open Target
This parameter is the rate, defined in seconds, at which a pulse will be
generated automatically by AUDMON for a source or client Consumer
(this parameter is ignored for a target or server Consumer). When
PULSERATE is set to 0, pulses will not be generated. When
PULSERATE is set greater than 0, pulse events will be generated for all
DBS objects with PULSEFILE ON even before the related Consumer
process has been started. This is done so that warnings can be produced
by AUDMON should the Consumer not get started. Note that some of
these early pulse events might not complete if a Collector skips the audit
trail locations where they were inserted. This can occur the first time you
start HP Shadowbase and an ADTSTARTxxx location is supplied, or you
Kommentare zu diesen Handbüchern