This feature enables Volume Replicator to monitor and control Non-Paged Pool memory (NPP) usage.
During replication, Volume Replicator uses the NPP memory for the following operations:
Stabilizing an incoming write from an application
Volume Replicator makes a copy of the application writes in VOLIOMEM pool as soon as a new write arrives. The pool gets memory from the Non-Paged Pool system memory.
Reading back the data from Replicator Log or data volumes
Volume Replicator may read back the data from the Replicator Log (in case of behind Secondary) or from the data volumes (in case of DCM mode replication) to send that data to Secondary. Buffer for both of these scenarios is allocated from the READBACK memory pool. The pool gets memory from the Non-Paged Pool system memory.
Holding the incoming updates on Secondary
Volume Replicator on Secondary stores the incoming writes from Primary in NMCOM pool. The pool gets memory from the Non-Paged Pool system memory. Among the three pools that are described, the VOLIOMEM pool is used by SFW as well as for serving mirrored volume writes and few other operations. Volume Replicator exclusively maintains and uses the READBACK and NMCOM pools.