This article applies to all JSDR software versions.
This article applies to all JSDR software versions.
The following alert message may be displayed if adequate space is not available in the replication log volume.
Each protected domain uses a single replication log for all the VMs belonging to it.
The replication log volume consists of multiple sections (described below):
Keeps a record of data being replicated to the object store.
I/O coming into the DRVA is written to the object store.
If there is a network bottleneck the I/O will get written to the replication log.
(It acts as a temporary placeholder.)
Contains metadata of the VMs including garbage collection (DB).
When metadata becomes full, if there is available free space in the replication log volume, the management server will automatically re-assign some of the free space to metadata.
The “log space low” message can appear when the replication log section is full or >90% for a certain period of time. This message will stop appearing once the space is freed up. |
Best Practices
|
If the replication log has been over provisioned, the replication log section can be resized to release free space on the replication log volume (RLV).
Starting with JSDR version 4.2, if the replication log volume becomes full and more space is required, it is possible to create additional free space on the replication log volume by simply increasing the disk size.
|