Skip to main content
commvault.com commvault.com
Solved

Is it normal to have the Time Shift Detected alert triggered with Live Sync?

PedroRocha
Byte
Forum|alt.badge.img+11

Hello,

 

Every time I run a Maintenance Failover, I receive the "CommServe Time Shift Detected !" alert.

 

Detected a change in the system time, it is now forwarded by 30 days 22 hours 32 minutes 10 seconds.

 

But there's no time shift between the active and standby Commserve servers…

 

Regards,

Pedro

Best answer by PedroRocha

I don't know why it happened, but this was the recommendation:

  1. Confirm timezones and time are the same in the active and standby commserves;
  2. perform a maintenance failover to the standby CS;
  3. on the standby CS, stop and start the Tomcat service via the cvlt process manager (when you start the Tomcat service, there is an alert regarding the supposed time shift, which does not exist - you confirm times are correct between the CSs);
  4. perform the maintenance failover failback;

That did the trick and no other time shift alerts when performing failovers

Regards,

Pedro

View original
Pedro
Did this answer your question?

6 replies

K
Vaulter
Forum|alt.badge.img+2

Hi @PedroRocha ,

Are you able to confirm the following:
- scheduled TLOG and replication jobs are completing with errors

- Is the Active and Standby CS both in the same Time Zone?

Thank you.

PedroRocha
Byte
Forum|alt.badge.img+11
  • PedroRocha
  • Author
  • Byte
  • 80 replies
  • May 5, 2023

Hello!

 

Yes!

SQL backups and replication jobs are running and finishing with success every 15 minutes:

 

Same Time Zone! UTC -3, both NTP synced, same date and time.

 

Regards,

Pedro

 

Pedro
Chris Hollis
Vaulter
Forum|alt.badge.img+15

@PedroRocha that’s very interesting… i think we need to take a closer look, are you in a position to be able to raise a support case so we can remote in?


Thanks

Chris 

PedroRocha
1 person likes this
  • PedroRocha
    PedroRocha
PedroRocha
Byte
Forum|alt.badge.img+11
  • PedroRocha
  • Author
  • Byte
  • 80 replies
  • May 8, 2023
Chris Hollis wrote:

@PedroRocha that’s very interesting… i think we need to take a closer look, are you in a position to be able to raise a support case so we can remote in?


Thanks

Chris 

I did that (230505-566)! Waiting on the engineer to contact me. Thanks.

Pedro
PedroRocha
Byte
Forum|alt.badge.img+11
  • PedroRocha
  • Author
  • Byte
  • 80 replies
  • Answer
  • May 8, 2023

I don't know why it happened, but this was the recommendation:

  1. Confirm timezones and time are the same in the active and standby commserves;
  2. perform a maintenance failover to the standby CS;
  3. on the standby CS, stop and start the Tomcat service via the cvlt process manager (when you start the Tomcat service, there is an alert regarding the supposed time shift, which does not exist - you confirm times are correct between the CSs);
  4. perform the maintenance failover failback;

That did the trick and no other time shift alerts when performing failovers

Regards,

Pedro

Pedro
Onno van den Berg
1 person likes this
  • Onno van den Berg
    Onno van den Berg
D
Bit
Forum|alt.badge.img+1
  • Dardan
  • Bit
  • 4 replies
  • November 30, 2023
PedroRocha wrote:

I don't know why it happened, but this was the recommendation:

  1. Confirm timezones and time are the same in the active and standby commserves;
  2. perform a maintenance failover to the standby CS;
  3. on the standby CS, stop and start the Tomcat service via the cvlt process manager (when you start the Tomcat service, there is an alert regarding the supposed time shift, which does not exist - you confirm times are correct between the CSs);
  4. perform the maintenance failover failback;

That did the trick and no other time shift alerts when performing failovers

Regards,

Pedro

 

The above stated is a workaround. The issue persists after performing a failover (monthly patching every ± 32 days).

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings