Solved

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

  • 19 May 2023
  • 4 replies
  • 560 views

Badge +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
 

icon

Best answer by Yashraj 19 May 2023, 13:25

View original

4 replies

Userlevel 4
Badge +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

Badge +2

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 ~]#

 

 

Badge

Hello @Baitos 

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

 

Badge +2

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!!!

Reply