+1 on the above. ...but before that, I would also scale back the frequency at least temporarily. Imagine for some reason or another you had a substantial amount of changed blocks, and that needed to replicate, yet, it couldn't be achieved in the 5 minutes before the next replica started.
I would kill the job, and try to replicate again. Again, I suspect it ws stepping on it's own toes after a large amount of changed block data. See if you can get another (or any) volume to replicate, and go from there.
sketchy00
203 Posts
0
August 17th, 2011 07:00
+1 on the above. ...but before that, I would also scale back the frequency at least temporarily. Imagine for some reason or another you had a substantial amount of changed blocks, and that needed to replicate, yet, it couldn't be achieved in the 5 minutes before the next replica started.
sketchy00
203 Posts
0
August 18th, 2011 15:00
I would kill the job, and try to replicate again. Again, I suspect it ws stepping on it's own toes after a large amount of changed block data. See if you can get another (or any) volume to replicate, and go from there.