Skip to main content
commvault.com commvault.com
Solved

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

B
Byte
Forum|alt.badge.img+2

Good morning,

I’m facing the same problem as it was resolved in 

I know this issue in production environment, where a commserve was not turned on for a long time, protecting against false dataaging. 
The solution to have a GUI Process manager opened and entering the string (I acknowledge and so on) is not available on my DEV-Env where I only use a UnixCommserver with the bash.

I tried to get the parameter within the commandline process manager commvault -all (and e.g. - I acknowledge and so on)

but unfortunately it is not available.

Did anyone have this problem as well?

Best regards
 

Best answer by Yashraj

Hello @Baitos 

You can delete the registry key lastSystemStoredTime registry key in .properties file under cvd registry.

 

View original
    F
    1 person likes this
    • F
      Farzin
    Did this answer your question?

    5 replies

    SparshGupta
    Vaulter
    Forum|alt.badge.img+10

    Hi @Baitos 

     

    Which service pack is this?

     

    If this is a Linux commserver, you need to run the command “commvault restart” as root user and enter the prompt. Perhaps, you should see something like this -

     



    Thanks,
    Sparsh

    J
    1 person likes this
    • J
      Jacek Piechucki
    B
    Byte
    Forum|alt.badge.img+2
    • Baitos
    • Author
    • Byte
    • 4 replies
    • May 19, 2023

    Hi,

    thanks for the help - see below info - this is 11.28.19

    [root@commserve ~]# commvault -all status
    --------------------------------- Instance001 ---------------------------------
    [ General ]
     Version = 11.28.19
     Media Revision = 1081
     CommServe Host Name = commserve
     CommServe Client Name = commserve
     Home Directory = /opt/commvault/Base
     Log Directory = /var/log/commvault/Log_Files
     Core Directory = /opt/commvault
     Temp Directory = /opt/commvault/Base/Temp
     Platform Type = 7
     Cvd Port Number = 8400
    [ Package ]
     1002/CVGxBase = File System Core
     1020/CVGxCommServe = CommServe
      - DB Directory = /opt/commvaultDB
      - DR Directory = /opt/commvaultDR
     1023/WorkFlowEngine = WorkFlow Engine
     1101/CVGxIDA = File System
     1118/CVGxGUI = CommCell Console
     1135/CVGxWebConsole = Command Center
     1136/CVGxVSA = Virtual Server
     1140/CvGxCloudConnector  = Cloud Apps
     1156/CVGxIndexingServer = Index Gateway
     1174/CVGxWebServer = WebServer
     1177/DiagnosticsAndUsageServer = Metrics Server
     1301/CVGxMA = MediaAgent
     1305/CVGxMACore = Storage Accelerator
     1306/CVGxAnalytics = Index Store
     1402/CVGxIntelliSnap = IntelliSnap
     1602/MessageQueue = Message Queue
     1604/MongoDB = MongoDB
    [ Physical Machine/Cluster Groups ]
     Name = commserve
      - Client Hostname = commserve
      - Job Results Directory = /opt/commvaultDB/jobResults
      - Index Cache Directory = /opt/commvault/MediaAgent/IndexCache
    [ Commvault Database ]
     851/CVGxCommServeDB = Commserve Database
     852/CVGxDM2WebServicesDB = DM2 Web Service Database
     854/CVGxWorkflowEngineDB = Workflow Engine Database
     855/CVGxCVCloudDB = Commvault Cloud Database
     856/CVGxCommServeHistoryDB = History Database
     857/CVGxResourceMgrDB = Resource Manager Database
     859/CVGxCommServeCacheDB = Cache Database
     861/CVGxCommserveAppStudioDB = App Studio Database
     863/CVGxCVCloudUsageHistoryDB = CVCloud Usage History DB
    [ Microsoft SQL Server ]
     Server Version = 15.0.4198.2
     Tool Version = 17.7.1.1
     MS ODBC Version = 17.7.2.1
    [root@commserve ~]# sudo commvault restart
    Redirecting stopping service for Instance001 to systemd ...
    Running "systemctl stop commvault.Instance001.service" ...
    Shutting redis server failed with error : 1
    Stopping Commvault services for Instance001 ...
    All services stopped.
    Cleaning up /var/log/commvault/Log_Files/locks ...
    Redirecting starting service for Instance001 to systemd ...
    Running "systemctl start commvault.Instance001.service" ...
    [root@commserve ~]#

     

     

    Y
    Vaulter
    Forum|alt.badge.img
    • YashrajVaulter
    • Vaulter
    • 1 reply
    • Answer
    • May 19, 2023

    Hello @Baitos 

    You can delete the registry key lastSystemStoredTime registry key in .properties file under cvd registry.

     

    F
    1 person likes this
    • F
      Farzin
    B
    Byte
    Forum|alt.badge.img+2
    • Baitos
    • Author
    • Byte
    • 4 replies
    • May 19, 2023

    I purged the entry in 

     /etc/CommVaultRegistry/Galaxy/Instance001/Cvd/.properties

    And Dataaging did not work. So checked the below entry: lastSystemStoredTime and set it to the actual Unixdate and Dataaging started!
    Thank your very much!!!

    F
    Forum|alt.badge.img
    • Farzin
    • 1 reply
    • September 4, 2024

    I faced the same for Commvault Version 11


    On win+r then "regedit”, go to this location

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\Cvd

    You will find "lastSystemStoredTime”. Delete that entry. (You can take a backup of your regestry)

    Try running the Data Aging job. It should work.

     

    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