When a MV/A session is stopped before it finishes, when it starts back up, it will start at 0% of what is left to transfer. If it finished 50% then fractured, when it starts, it will show it starting at 0%, but this is 0% of the remaining 50%.  If the RLPs on the destination side run our of capacity, you will fracture and not finish update. You must have sufficient RLP to hold the "Gold" copy of the last successful update, before a new update starts. You always want to be able to fail back to the last, good update. You need to increate the RLP on the destination array.  glen
I have 4 luns configured for mirrorview/A replication , initial synch completed , however for the last  about 2 months (May 4th 2011) it has never updated  date and time , What i have noticed is that  replication restarts from   0% whenever the link goes down and rarely goes beyond 10% , From the mirrorview /A documentation  , it shows  all the changes are saved on RLP  and  should the link go down  it resumes from where it stopped , Could there be any setting missed out while configuring the remote  mirror ?  
Mirrorview/ A time stamp not updating