Unsolved
1 Rookie
•
10 Posts
0
1209
October 8th, 2019 06:00
RP4VMs journal sizing during network interuption
Hi,
We have a large environment change coming soon which will involve a protracted outage of connectivity (perhaps a working day) between our production site and our DR site and all the target VRPAs being shutdown.
Currently we have 1-way RP4VMs protection, say from A to B. Due to bandwidth limitations we're keen to involve as little 're-sync' traffic (and time) as possible.
Our plan currenrlty is to pause all the CGs before the outage starts, then the site B VRPAs can be shutdown. Once work has been completed we will power up all the site B VRPAs again and just resume the CGs.
Hopefully this will mean no need for a long re-sync and everything should go back to 'active' pretty quickly?
Is this the best procedure for this please? Is there anything that affects how long the second site can be offline for before the re-sync starts to take a longer time?
Does it matter how large the source (site A) journals are - i.e. will increasing the size of the journals make any difference to the above or is that not relevant here?
Cf-arar
3 Posts
0
October 27th, 2019 08:00
Hi Wee jim,
Any answer or advice for your question ? i have the same scenario but the replication is down for 4 month, do u mean that the journal size must be very big to catch the difference quickly between production and DR ? Thanks
Idan
3 Apprentice
•
675 Posts
0
October 27th, 2019 13:00
Hi,
No need to size the journals for such cases as we're marking data on the production journal. This means that only offsets are written to the production journals or in other words, only location of blocks in the production volumes which have changed. Once the link is back up, we simply read from the production volumes based on the prod journal bitmap.
Hope that helps,
Idan