Skip to main content
commvault.com commvault.com
Solved

Data Aging - Failed to run Data Aging job due to change in system time.

  • September 12, 2022
  • 9 replies
  • 4547 views
S
Byte
Forum|alt.badge.img+2

Hello All,

My apologies in advance if this ends up being something super simple.

Commvault seems to be throwing this error when attempting Data Aging:

Time difference between current time and last stored time in seconds : [3184347]
checkTimeShift() - Forward System time shift is greater than 1 day.
IsTimeShiftDetected() - Setting Cvd/isTimeShiftDetected registry key to [1]
Failed to run Data Aging job due to change in system time.

The time and date (as well as the time-zone) are correct on Commserve.

Has anyone encountered this before?
I’ve searched FAQs and I’m hoping there’s something I missed.

Best answer by Scott Moseman


Confirming CommServe Server Time Change
https://documentation.commvault.com/2022e/expert/150320_confirming_commserve_server_time_change.html

I cannot answer why your time may have changed, but you should be able to clear this by restarting the CV services and accepting the prompt warning about the time change.

This is a security setting which helps prevent someone or something from changing the CS time in an attempt to prematurely age backup data.

Thanks,
Scott

View original
Did this answer your question?

9 replies

Scott Moseman
Vaulter
Forum|alt.badge.img+18
  • Scott MosemanVaulter
  • Vaulter
  • 502 replies
  • Answer
  • September 12, 2022


Confirming CommServe Server Time Change
https://documentation.commvault.com/2022e/expert/150320_confirming_commserve_server_time_change.html

I cannot answer why your time may have changed, but you should be able to clear this by restarting the CV services and accepting the prompt warning about the time change.

This is a security setting which helps prevent someone or something from changing the CS time in an attempt to prematurely age backup data.

Thanks,
Scott

Commvault Enterprise Success
Mike Struening
S
2 people like this
  • Mike Struening
    Mike Struening
  • S
    Steve P
Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Jos MeijerCommvault Certified Expert
  • Commvault Certified Expert
  • 638 replies
  • September 12, 2022

Do you use a time server to sync with?

Mike Struening
S
2 people like this
  • Mike Struening
    Mike Struening
  • S
    Steve P
Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Damian AndreVaulter
  • Vaulter
  • 1290 replies
  • September 13, 2022

If your CommServe is a VM, it could have moved to a different host where the time is dramatically different - the guest tools (i.e VMware Tools) automatically tries to sync the time with the host. That could be the reason why this happened without any changes to the machine.

I would check the application or system logs on the server to see if there are any clues.

 

Mike Struening
Jos Meijer
S
3 people like this
  • Mike Struening
    Mike Struening
  • Jos Meijer
    Jos Meijer
  • S
    Steve P
S
Byte
Forum|alt.badge.img+2
  • Steve P
  • Author
  • Byte
  • 5 replies
  • September 13, 2022

Thank you Scott, Data Aging has completed successfully.

Thanks as well to Jos and Damian for the additional input,  yes it syncs with a time server and you assumed correctly CommServe is a VM and that could totally be what could definitely be the underlying cause.

Mike Struening
1 person likes this
  • Mike Struening
    Mike Struening
B
Forum|alt.badge.img
  • boni
  • 1 reply
  • December 19, 2022

I have failed.

system has been off for a long time


Please give specific guidance.

 

11.28.24

Commserve - Linux Server

 

 

 

 

HenkR
Byte
Forum|alt.badge.img+5
  • HenkR
  • Byte
  • 26 replies
  • March 26, 2023

Well I encountered this also in my lab.

Restart Commserve services in the Process Manager and accept your worst nightmare.

Luckily it's just my lab. 

 

 

L
1 person likes this
  • L
    Laurent
C
Vaulter
Forum|alt.badge.img+1
  • CSFVaulter
  • Vaulter
  • 4 replies
  • May 10, 2023

I have Live Sync between a physical server and a VM running on a different server.  Not sure if the time on the VM was different at one point or not and perhaps that is what caused this issue.  The active CommServe has been on the physical server for probably the past year at this point.  I still get the message if I stop the services in Process Manager (yes I can always start the services one by one via Windows Services but that’s a tad painful).  I filtered the log and found the following. The time on my physical server is correct but I guess it conflicts with the database. 

 

The better question is how to fix it?

 

C
Vaulter
Forum|alt.badge.img+1
  • CSFVaulter
  • Vaulter
  • 4 replies
  • May 10, 2023

I know about the string.  It fails even when I copied it out of another ticket.

 

This is on 11.30.40

C
Vaulter
Forum|alt.badge.img+1
  • CSFVaulter
  • Vaulter
  • 4 replies
  • May 10, 2023

Updated the Last Stored System Time with the current time as given to me by:

https://www.epochconverter.com/

and reset the time shifted back to 0

Error addressed.

 

Nikos.Kyrm
1 person likes this
  • Nikos.Kyrm
    Nikos.Kyrm

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