vSphere Replication Configuration fails, error - Time skew between machine and vCenter server is too large
search cancel

vSphere Replication Configuration fails, error - Time skew between machine and vCenter server is too large

book

Article ID: 393333

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

  • While configuring vSphere Replication error appears:

  • NTP configured on vSphere Replication server

Environment

VMware vSphere replication 8.x
VMware vSphere replication 9.x
VMware Live Recovery 8.x
VMware live Recovery 9.x

Cause

  • This problem arises when the time of vSphere replication differs from the time of vCenter Server.

  • Additionally, this issue may also occur if NTP (Network Time Protocol) synchronization between the VR/SRM and vCenter Server is not functioning correctly or disabled.

Resolution

Perform the below steps:

1. Login to vSphere Replication VAMI -> Select NTP.

2. Select the Time zone and edit. For Time Synchronization select edit and enable NTP.

3. Enter the NTP server IP or hostname, click save.

4. Repeat the same steps for vCenter Server using VAMI.

5. Using vSphere replication VAMI , Summary - >Configure Appliance run Configuration.

6. Fill Details necessary and use "Finish" to complete the configuration step.

For reference Configure the Time Zone and Time Synchronization Settings for the vSphere Replication Appliance

Workaround:

Steps to change the date and Time of SRM/VR manually

1. Capture vCenter server appliance date and time,

$ watch date - this output gives current time.

Note: the same command needs to be run on other appliances having issues.

2. To manually change use below command

$ date --set="YY-MM-DD HH:MM:SS" 

3. Restart NTP services,

$service ntpd stop

$service ntpd start

$service ntpd status