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

Version 1 Next »

This article applies to (all JSDR software versions / JSDR software version(s) xx.xx.xx)

\uD83E\uDD14 Problem

The DRVA system captures and transfers data changes to blob storage. Any disruptions, including reboots of the DRVA VM or its services, generate alerts in vCenter. Promptly understanding and addressing these alerts is essential to maintain DR operations, data integrity, and replication continuity.

image-20240618-141525.png

Note: This is an info alert likely the DRVA should be up by itself. Validate and ensure all status reported good

đŸ’¡ Cause

  1. Unexpected reboot of the DRVA.

  2. DRVA services are down

  3. Loss of connectivity to the DRVA due to brief network interruptions

\uD83C\uDF31 Solution

  1. Access JetStream UI:

    • Log in to the JetStream DR UI.

    • Navigate to the Appliances section.

    • Check the status of the DRVA.

  2. Check DRVA VM Status:

    • Access the vCenter environment and locate the DRVA VM.

    • Verify that the DRVA VM is powered on and functioning.

    • By taking console access to DRVA VM check if the DRVA service is running systemctl status drva.

    • Verify MSA is able to reach DRVA management network

  3. Performance Monitoring:

    • Use monitoring tools to check CPU, memory, and disk usage on the DRVA.

  4. Ensure replication status under the protected domain is intact.

Note: The decision to reboot the DRVA should be made by JetStream Support after reviewing the logs.

  • No labels