HP XP P9500 Software User's Manual page 88

2. The copy group starts being suspended when the 10:00:05 update journal, which was
created after the CAJ ATTIME suspend time (10:00:00), is detected.
The 10:00:05 update journal is not reflected into the volume at the secondary site, because
the copy group has already been suspended.
When a no-update journal is detected after the specified CAJ ATTIME suspend time on the
secondary site
As indicated in
detected after the specified CAJ ATTIME suspend time on the secondary site.
NOTE:
Figure 51 Copy-group suspension when a no-update journal is detected after the specified
CAJ ATTIME suspend time
In Figure 51 (page
1. The data in the 09:59:58 update journal is reflected into the volume at the secondary
site, because the ATTIME suspend time (10:00:00) has not been reached yet.
2. The copy group starts being suspended after 10:00:00, when the no-update journal is
detected.
The 10:00:10 update journal is not reflected into the volume at the secondary site, because
the copy group has already been suspended.
When timeout occurs:
As indicated in
secondary site, if neither an update journal nor a no-update journal is detected due to the
disconnection of the paths or other reasons, copy-group suspension will be executed after the
specified timeout time has elapsed from the ATTIME suspend time.
When journals are being reflected into the volume at the remote site, if the timeout time has
expired for a reason such as timeout time shortage or too many update journals, copy-group
suspension will be executed without waiting for the journal reflection to finish.
88 Understanding Business Continuity Manager functions
Figure 51 (page
A no-update journal indicates that an update did not occur.
88), the specified ATTIME suspend time is 10:00:00, so:
Figure 52 (page
88), suspension is executed when a no-update journal is
89), when journals are being reflected into the volume at the