Versions Compared

Old Version 17

changes.mady.by.user Anthony Lai

Saved on

compared with

New Version Current

changes.mady.by.user Anthony Lai

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article applies to all JSDR software versions.

Issue

The following alarm alert 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 the VMs belonging to it.

  • The replication log volume consists of multiple sections (illustrated described 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 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).

Free Space Section

  • When Metadata metadata becomes full, if there is available Free Space free space in the replication log volume, the management server will automatically re-assign some of the Free Space free space to Metadatametadata.

Note

The “log space low” message can appear when the Replication Log Section replication log section is full or > 90% >90% for a certain period of time. This message will stop appearing once the space is freed up.

Info

Best Practices

  • The Replication Log 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.

...

If the replication log has been over provisioned, it the replication log section can be resized to release free space on the replication log volume (RLV).

...