Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

This article applies to all JSDR software versions.

Issue

The following alarm message may be displayed if adequate space is not available in the replication log volume.

Details of a Replication Log Volume

  • Each protected domain uses a single replication log for all its VMs.

  • The replication log volume consists of multiple sections (illustrated below):

Replication Log Section

  • 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.)

Metadata Section

  • Contains metadata of the VMs including garbage collection (DB).

Free Space Section

  • 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 Practice

  • Replication log section should be sized to 64GB per protected domain (regardless of the number of VMs being protected).

  • The number of vDisks protected should not exceed 500 per DRVA.

Example

User can re-size the Replication Log size if it is highly provisioned, it will release some space on the RLV (Replication log volume).

Future enhancements:
From JetDR 4.2 onwards, if the Replication log volume is full and more space is required, users can shut down the drva, increase the disk size from VM → Edit Settings and then power it on. This will add more space to the Replication log volume.

  • No labels