 | ||
| Determining the size of the Replicator Log | ||
|---|---|---|
| Prev | Sizing the Replicator Log | Next |
To determine the size of the Replicator Log, you must evaluate each of the following constraints individually. Then, choose a value at least equal to the maximum so that all constraints are satisfied.
Note: |
If the size of the Replicator Log specified is not enough to meet new business requirements, then you can resize the Replicator Log. |
For more information,
To determine the size of the Replicator Log, you need the following information:
The maximum expected downtime for Secondary nodes.
The maximum expected downtime for the network connection.
The method for synchronizing Secondary data volumes with data from Primary data volumes.
If the application is shut down to perform the synchronization, the Replicator Log is not used and the method is not important. Otherwise, this information can include, the time that is required to copy the data over a network, or the time that is required to copy it to a tape or disk, to send the copy to the Secondary site, and to load the data onto the Secondary data volumes.
Note that if you use the option from VEA to synchronize the Secondary the previous paragraph is not a concern.
In the case of Secondary data volume failure if you perform Secondary backup to avoid complete synchronization, the information needed includes the following:
The frequency of Secondary backups.
The maximum expected delay to detect and repair a failed Secondary data volume.
The expected time to reload backups onto the repaired Secondary data volume.
More Information