New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Absent Member.
Absent Member.
808 views

HP Storage Essentials unable to discover Backup Manager(HP Data Protector)

I am working with HP Storage Essentials v6.0. I am facing an issue where HPSE is unable to discover the Backup Manager(HP Data Protector) that I have installed on the same server.

Has anyone faced similar problem and found a solution? If yes, please let me know at asap. Any kind of help will be greatly appreciated.

 

 

P.S. This thread has been moved from Storage Area Networks (SAN) (Enterprise) to Storage Essentials Support and News Forum. - Hp Forum Moderator

0 Likes
9 Replies
Highlighted
Absent Member.
Absent Member.

Hi,
what OS is the DP cell cerver installed at pls?
the pain is one part of the reality
0 Likes
Highlighted
Absent Member.
Absent Member.

Windows server 2003
0 Likes
Highlighted
Absent Member.
Absent Member.

was it upgraded from the 5.1 version pls?
the pain is one part of the reality
0 Likes
Highlighted
Absent Member.
Absent Member.

No
0 Likes
Highlighted
Absent Member.
Absent Member.

you can try the following:

-stop the AppStorWin32Agent service
-the CIMextension will create a cachedb directory within DataProtectors database (db40)directory and start an
internal scheduler to prefetch DataProtector information. When for some reason this directory 'cachedb'
is already present due to older Cim Extenstions within the db40 directory, delete it before starting the
CIMextension.
-the cachedb directory will be recreated.
-After that run a GAED on the CellManager host with Backup Details included, twice ( 2 times !)
it should then start to populate the Backup Manager with DP data.

if it does not help you can send the GAED logs to the HP SE support centre for the analysis
the pain is one part of the reality
0 Likes
Highlighted
Absent Member.
Absent Member.

Thanks for help. Now, the Storage Essentials is able to discover the backup manager however the backup manager schedules are unable to discover the session details from the backup manager. When I run the 'session collection" schedules the status says "Session collection failed".

Please provide some help on this.
0 Likes
Highlighted
Absent Member.
Absent Member.

I am getting following error logs. Please see the attached error logs
0 Likes
Highlighted
Absent Member.
Absent Member.

Here are more logs. I think these make more sense.
getClass(":APPIQ_BackupClient", false, true, null)
[2008-09-12 11:55:18] INFO [ClientForCxwsAgent-16 com.appiq.cxws.agency.patron.PatronValueReader] 172.16.49.203:4673 102 yields FAILURE_RESPONSE_MSG:
[2008-09-12 11:55:18] INFO [ClientForCxwsAgent-16 com.appiq.cxws.agency.patron.PatronValueReader] ProviderSpecificException with 1 argument(s).
[2008-09-12 11:55:18] INFO [ClientForCxwsAgent-16 com.appiq.cxws.agency.patron.PatronValueReader] MessageOnlyException with 1 argument(s).
[2008-09-12 11:55:18] WARN [ClientForCxwsAgent-16 com.appiq.wbemext.client.ClientForCxwsAgent] Trouble while processing response for 172.16.49.203:4673 102
[2008-09-12 11:55:18] ERROR [Thread 2 com.appiq.service.synchronizer.utils.Replicator] cxws://172.16.49.203 : ERROR replicating APPIQ_BackupJob instances
com.appiq.cxws.exceptions.ProviderSpecificException: Provider com.appiq.providers.backup.BackupJobProvider for root/cimv2:APPIQ_BackupJob failed.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.appiq.cxws.agency.patron.PatronValueReader.readOneException(PatronValueReader.java:67)
at com.appiq.cxws.agency.patron.PatronValueReader.readException(PatronValueReader.java:38)
at com.appiq.wbemext.client.ClientForCxwsAgent.process(ClientForCxwsAgent.java:1066)
at com.appiq.wbemext.client.ClientForCxwsAgent$AgentResponseTask.run(ClientForCxwsAgent.java:146)
at com.appiq.cxws.utils.ThreadPool$PoolThread.run(ThreadPool.java:210)
Caused by: com.appiq.cxws.exceptions.MessageOnlyException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.appiq.cxws.agency.patron.PatronValueReader.readOneException(PatronValueReader.java:67)
at com.appiq.cxws.agency.patron.PatronValueReader.readException(PatronValueReader.java:42)
... 3 more
[2008-09-12 11:55:18] DEBUG [Thread 2 com.appiq.dataModel.TaskData] cxws://172.16.49.203 : ERROR replicating BackupJob instances
[2008-09-12 11:55:18] DEBUG [Thread 2 com.appiq.dataModel.TaskData] Thread 2 (cxws://172.16.49.203): BackupJob details retrieved
[2008-09-12 11:55:18] DEBUG [Thread 3 com.appiq.wbemext.client.AppiqCimClient.cxws] [Thread 3] Client cxws://172.16.49.203/root/cimv2 (27) exiting call 0: getClass; Return Value: class APPIQ_BackupClient (21 total properties; 6 keys)
[2008-09-12 11:55:18] DEBUG [Thread 4 com.appiq.service.synchronizer.utils.Replicator] CIMgetClass: APPIQ_BackupSchedule
[2008-09-12 11:55:18] DEBUG [Thread 4 com.appiq.wbemext.client.AppiqCimClient.cxws] [Thread 4] Client cxws://172.16.49.203/root/cimv2 (25) entering call 1: getClass(":APPIQ_BackupSchedule", false, true, null)
0 Likes
Highlighted
Absent Member.
Absent Member.

More logs:


<> 49575
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.