On the DR (Disaster Recovery) SRM (Site Recovery Manager) site, recovery plan steps are not visible, and the option to test is greyed out. Initiating the SRM test from the primary site completes without errors. Direct access to SRM and VR (vSphere Replication) via the following URLs is functional:
https://<SRM IP Address>/dr
https://<VR IP Address>/dr
Symptoms:
Unable to retrieve Site Recovery Manager summary data. Unable to log in to 'Site Recovery Manager Server at https://##-###-######-01.######.net:443/drserver/vcdr/vmomi/sdk'.
#######-1234-5678-9011-############
8/31/24, 5:55:55 AM +0000
A runtime error occurred in vSphere Server
. Exception details: 'Invalid message timestamp, created time is in the future' "Unable to retrieve Site Recovery Manager summary data"
can occur due to a time skew issue between the vCenter Server and Site Recovery Manager (SRM). This is typically indicated by the error message: "Time skew between this machine and the vCenter Server is too large."
Move the DR vCenter VM and SRM to the Same ESXi Host: Place both the DR vCenter Server VM and the SRM appliance on the same ESXi host to minimize potential time synchronization discrepancies.
Update NTP Settings on DR SRM: Configure the NTP settings on the DR SRM appliance to match the ESXi host's time settings. This ensures that the SRM appliance is synchronized with the host time.
Adjust vCenter Time Settings: Update the time settings on the vCenter Server to match the ESXi host time. This alignment ensures consistent time synchronization across the infrastructure.
Reconfigure SRM: After completing the above steps, reconfigure SRM to resolve any remaining synchronization issues and verify that the time sync problem between the vCenter Server and SRM is resolved.
Refer: Configure the Time Zone and Time Synchronization Settings for the Site Recovery Manager Appliance