The production and target journal can be of different sizes. Journals can be as small as 10GB. The requirement on production journal will depends on the retention the solution need to have after failover (when the production journal becomes the target one).
the datastore housing some or all of the journal VMDKs can be dedicated or shared. The decision on whether to dedicate it in general or b/w CGs will depend on the production workload and consequently the target journal required performance.
Correct on the fact that during a full sweep after the CG is enabled, the journal is bypassed, writes are going directly to the target volumes. This is called fast first-time initialization. Although target journal performance isn't related to the performance of an initial sync, it is vital to perform a proper sizing exercise to make sure that required RPO can be met.
Journal are being used in a cyclic manner so old PiTs will be overwritten by new ones.
Idan
3 Apprentice
•
675 Posts
0
February 25th, 2015 05:00
Hello there,
The production and target journal can be of different sizes. Journals can be as small as 10GB. The requirement on production journal will depends on the retention the solution need to have after failover (when the production journal becomes the target one).
the datastore housing some or all of the journal VMDKs can be dedicated or shared. The decision on whether to dedicate it in general or b/w CGs will depend on the production workload and consequently the target journal required performance.
Correct on the fact that during a full sweep after the CG is enabled, the journal is bypassed, writes are going directly to the target volumes. This is called fast first-time initialization. Although target journal performance isn't related to the performance of an initial sync, it is vital to perform a proper sizing exercise to make sure that required RPO can be met.
Journal are being used in a cyclic manner so old PiTs will be overwritten by new ones.
Hope that helps,
Idan