omnisv -status
ProcName Status [PID]
==============================
crs : Active [4952]
mmd : Active [2596]
kms : Active [4076]
hpdp-idb : Active [5104]
hpdp-idb-cp : Active [3740]
hpdp-as : Down <<<<<<<<<<<<<<<<<<<<<<<<<<
omniinet : Active [3888]
Sending of traps disabled.
==============================
Status: At least one of the Data Protector processes/services is not running.
hpdp-as
The Data Protector Application Server (hpdp-as) service is used for connecting the GUI to the IDB through a HTTPS connection (web services). It runs on the Cell Manager and has a local connection to the hpdp-idb-cp service.
=> CM is up but cu cannot run DP GUI.
From logs :
boot.log
08:11:22,663 ERROR [org.jboss.as.controller.management-operation] Operation ("add") failed - address: ([("deployment" => "jce-serviceregistry.war")]) - failure description: "JBAS018717: No deployment content with hash 37f0daa24663c15e2581f39d35619f98c6b179e8 is available in the deployment content repository for deployment 'jce-serviceregistry.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart.."
run.log
08:11:22,663 ERROR [org.jboss.as.controller.management-operation] Operation ("add") failed - address: ([("deployment" => "jce-serviceregistry.war")]) - failure description: "JBAS018717: No deployment content with hash 37f0daa24663c15e2581f39d35619f98c6b179e8 is available in the deployment content repository for deployment 'jce-serviceregistry.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart.."
It is pointing to the file jce-serviceregistry.war.
This file is in the
Directory of C:\Program Files\OmniBack\bin\components
09/27/2015 07:49 AM <DIR> .
09/27/2015 07:49 AM <DIR> ..
10/07/2014 10:23 AM 2,451,770 dp-jobexecutionengine-backup.war
02/05/2014 04:02 AM 2,238,058 dp-jobexecutionengine-consolidation.war
02/05/2014 04:02 AM 2,237,948 dp-jobexecutionengine-copy.war
02/05/2014 04:02 AM 2,238,186 dp-jobexecutionengine-verification.war
02/05/2014 04:02 AM 3,027,539 dp-loginprovider.war
02/05/2014 04:02 AM 17,228,657 dp-scheduler-gui.war
12/09/2014 03:01 AM 3,533,744 dp-webservice-server.war
02/05/2014 04:02 AM 3,241,222 jce-dispatcher.war
02/05/2014 04:02 AM 2,121,244 jce-serviceregistry.war
12/11/2014 12:25 AM 2,616,488 ormapper.dll
12/11/2014 12:28 AM 3,045,032 PocoLogger.dll
12/11/2014 12:28 AM 2,786,984 ScaContainer.dll
12/11/2014 12:28 AM 2,312,872 SerializerBasic.dll
12/11/2014 12:29 AM 2,130,600 SerializerFwsTypes.dll
12/11/2014 12:29 AM 2,814,120 ServiceFactory.dll
15 File(s) 54,024,464 bytes
2 Dir(s) 84,904,427,520 bytes free
File is in the DP HOME DIRECTORY - where all binary executable file reside.
DP_HOME_DIR=C:\Program Files\OmniBack\
Customer shared information that this is DR server and they are trying to restore IDB (from the PROD CM).
After many denials from different member of the customer team, one of them admitted they've made changes on C:\Program Files\OmniBack\.
Since they just need to restore + recover IDB (from an IDB backup tape) into a newly installed and functional CM (replacing the blank IDB), they only need to touch files inside the DP_DATA_DIR=C:\ProgramData\OmniBack\ directory.
FIX
Redo all steps and ensure only related IDB files will be updated/changed or touched. Only files inside DP_DATA_DIR=C:\ProgramData\OmniBack\ directory.
Dont make any changes on DP_HOME_DIR=C:\Program Files\OmniBack\ when doing an IDB restore/recover.