DRVA Restarted

This article applies to all JSDR software versions.

Alarm

This alarm signals disruption to the DRVA VM or its services, including reboots. Understanding and promptly addressing issues indicated by this alarm is essential to maintaining proper DR operation, data integrity, and replication continuity.

Possible Cause

• Unexpected reboot of the DRVA.
• DRVA services are down.
• Loss of connectivity to the DRVA due to network interruption.

Resolution

1. Access the JetStream DR UI.
   • Log in to the JetStream DR UI.
   • Navigate to the Appliances section.
2. Check the status of the DRVA VM.
   • Access the vCenter environment and locate the DRVA VM.
   • Verify that the DRVA VM is powered on and functioning.
   • From the console, access the DRVA VM and check if its service is running using the command: systemctl status drva.
   • Verify the MSA is able to connect to the DRVA management network.
3. Check performance of the DRVA.
   • Use monitoring tools to check CPU, memory, and disk usage on the DRVA.
4. Validate the replication status of the protected domain.
   • The replication status should be consistent with the current state of the DR process.

Contact Jetstream Support and provide MSA logs if you are unable to resolve the issue.
It is not advised to reboot the DRVA unless instructed to do so by JetStream Support.