Once the replication is started with a checkpoint, even the checkpoint is subsequently overflowed, the replication should not be affected.

The following is a demonstration that the overflowed checkpoint will not affect the replication which was started with it.   That is to sayt hat you don't have to worry about checkpoint overflow once the replication is started.

1. Synchronizing the data volume with a RVG checkpoint.

#vradmin -g vvr1dg -c ckptA -full syncrvg rvg1 alaw2bge3
Message from Hostalaw2bge3:
VxVM VVR vxrlink WARNING V-5-1-3532 Rlink rlk_alaw1bge3_rvg1 is already detached
Message from Primary:
VxVM VVR vxrsync INFO V-5-52-2232Starting full volume synchronization to remote
VxVM VVR vxrsync INFOV-5-52-2211    Source host:        192.168.33.1
VxVM VVR vxrsync INFO V-5-52-2212    Destination host(s): 192.168.33.2
VxVM VVR vxrsync INFO V-5-52-2213    Total volumes:       2
VxVM VVR vxrsync INFOV-5-52-2214    Total size:          210.000M
Eps_time Dest_host       Src_vol    Dest_vol     F'shed/Tot_sz  Diff  Done
00:00:01192.168.33.2    vvol11      vvol11          0M/110M      --    0%
00:00:03192.168.33.2    vvol11      vvol11        110M/110M      --  100%
00:00:03192.168.33.2    vvol12      vvol12          0M/100M      --    0%
00:00:06192.168.33.2    vvol12      vvol12        100M/100M      --  100%
VxVM VVR vxrsync INFO V-5-52-2219VxRSync operation completed.
VxVM VVR vxrsync INFO V-5-52-2220 Total elapsed time: 0:00:06

# vxrvg -g vvr1dg cplistrvg1
Name                    MBytes  %Log  Started/Completed
----                    ------  ------  -----------------
ckptA                  193     97      Completed

2. Starting the replication with checkpoint

# vradmin -g vvr1dg -c ckptA startreprvg1
Message from Primary:
VxVM VVR vxrlink INFO V-5-1-3614 Secondary data volumes detected with rvg rvg1 as parent:
VxVM VVR vxrlink INFO V-5-1-6183 vvol11:      len=225280              primary_datavol=vvol11
VxVM VVR vxrlink INFO V-5-1-6183 vvol12:      len=204800              primary_datavol=vvol12

3. Overflowing the checkpoint with additional I/Os.

# vxrvg -g vvr1dg cplistrvg1
Name                    MBytes  %Log  Started/Completed
----                    ------  ------  -----------------
ckptA                  

4. As long as the SRL continues to be drained and the SRL itself doesn't overflow, the rlink will become consistent when the rlink is up-to-date.

VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlk_alaw2bge3_rvg1 has 719 outstanding writes, occupying 156455 Kbytes (76%) on the SRL
....
VxVM VVR vxrlink INFO V-5-1-4467 Rlink rlk_alaw2bge3_rvg1 is up to date

5. The rlink will become consistent eventually even the checkpoint was overflowed during starting stage of the replication.

#vxprint -g vvr1dg -lP rlk_alaw2bge3_rvg1
Rlink:    rlk_alaw2bge3_rvg1
info:    timeout=500 packet_size=8400rid=0.1877
         latency_high_mark=10000latency_low_mark=9950
         bandwidth_limit=none
state:    state=ACTIVE
         synchronous=offlatencyprot=offsrlprot=autodcm
assoc:    rvg=rvg1
         remote_host=alaw2bge3IP_addr=192.168.33.2port=4145
         remote_dg=vvr2dg
         remote_dg_dgid=1166620333.99.alaw2
         remote_rvg_version=30
         remote_rlink=rlk_alaw1bge3_rvg1
         remote_rlink_rid=0.2017
         local_host=alaw1bge3IP_addr=192.168.33.1 port=4145
protocol: UDP/IP
checkpoint:ckptA
flags:    write enabled attached consistent connected asynchronous    <<< consistent

# vxrvg -g vvr1dgcplistrvg1
Name                    MBytes  %Log  Started/Completed
----                    ------  ------  -----------------
ckptA