HI Bob,
You are right, the standalone.xml file was generated in "Program Data -> Omniback -> Config -> Server -> AppServer" and i have been searched in "Program Files".
After change the "management interface" from 127.0.0.1 to 0.0.0 the service "Data Protector Appserver" doesn't initialize.
This is my test environment, any idea beacuse the service don't make up ?
Diogo
Hello Guys,
I have the date Proctor 7 and was using the 6.0.2 version of XenServer, now upgraded to version 6.2 of XenServer VMs and my backups stopped doing.
The DataProtector is compatible with XenServer 6.2?
Thanks.
José Francisco
I am hacving exactly the same issue and clearing the cache has made no difference for me.
Any other ideas?
hi,
your OS only see tape drive, if you have SAN check the zone, looks like someting is bad in your configuration.
need to show someting like Bob said:(this is robot)
Exch HP:1x8 G2 AUTOLDR Path: "/dev/rac/c0t4d1" SN: "MXA94210HN"
Description: HP StorageWorks 1x8 Cartridge Autoloader
Revision: 2.80 Flags: 0x0006 Slots: 7 Drives: 1
Drive(s) SN:
"HU10938F7R"
Regards
Hi Bob,
Thanks for your anwer.
I will try other options and if I find any solutions , will let you know.
Regards
None that I am aware of, but, aggain, I have to defer to the hardware vendor on questions like this
You may want to make a copy of the 'standalone.xml' file before starting any of this, because all setting are going to need to be reset after tracing is done, and it may be easier to just replace the file with th eoriginal version
In the 'standalone.xml' file enable tracing:
change the logging level to "TRACE" for the periodic rotating file handler named "FILE":
<periodic-rotating-file-handler name="FILE">
<level name="TRACE"/>
Second, a category needs to be added to the logging subsystem for
org.jboss.security to be able to trace JBoss security issues:
<logger category="org.jboss.security">
<level name="TRACE"/>
</logger>
Third, the logging for DP specific logs should be set to trace level. This will enable trace level logs for the logs from
DpLoginModule
<size-rotating-file-handler name="DP_LOGGER" autoflush="true">
<level name="TRACE"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%C{1}:%L:%t] %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="DPServer.log"/>
<rotate-size value="10M"/>
<max-backup-index value="5"/>
<append value="true"/>
</size-rotating-file-handler>
Fourth, a category needs to be added to the logging subsystem for
com.hp.im to be able to trace DpLoginModule issues:
HP Data Protector 8.10 Update Training–LDAPIntegration and Certificates
<levelname="TRACE"/><formatter><pattern-formatterpattern="%d{HH:mm:ss,SSS}%-5p
[%C{1}:%L:%t]%s%E%n"/></formatter><filerelative-to="jboss.server.log.dir"path="DPServer.log"/><rotate-sizevalue="10M"/><max-backup-indexvalue="5"/><appendvalue="true"/>
</size-rotating-file-handler>
Fourth, a category needs to be added to the logging subsystem for
com.hp.imtobe able to trace DpLoginModuleissues:
<loggercategory="com.hp.im"><levelname="TRACE"/></logger>
Save the 'standalone.xml' file. The log file traces will be written to is:
Program Data -> Omniback -> Config -> log -> AppServer -> server.log
A successful login should look like this:
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000220: Logging into LDAP server with env (…)
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000268: Assigning user to role (…)
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000241: End login method, isValid: true
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000236: Begin initialize method
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000240: Begin login method
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000242: Begin commit method, overall result: true
TRACE [org.jboss.security] (http--0.0.0.0-7116-11) PBOX000242: Begin commit method, overall result: true
If it shows anything different, and I am sure that it will, you will need to open a case with the response center, and it will probably need to be elevated to Engineering. It is just that I am not sure if anyone there would know how to implement tracing. You should probably keep a copy of your edited 'standalone.xml' file also in case they want you to do additional tracing
If you want me to look at your 'server.log' file, I certainly will to see if what you have is a know problem, just send it as an attachment to this forum thread
A look at the Data Protector Virtualization support matrix
http://support.openview.hp.com/selfsolve/document/KM1357659
show this for Xen
Citrix - Citrix XenServer 4.1, 5.0, 5.5, 5.6, 6.0
I guess that 6.0.2 was not enough of a difference from 6.0 to matter to Data Protector, but, when you upgraded to Xen 6.2, it became an unsupported configuration. I would imagine that it will be supported in the future, I have no idea of when
I suggest that you Bookmark the above URL, and check the support matrix periodically
Thanks for your answers.
So it's not very important Ifi can notbeexport beforethe relocation, becauseI canmanually edit theregeditand thenimport it into theGUICMb.
Hello all....one of my clients is looking for options to back up their SQL 2008 Data Bases, they use Micorosft TDE to encrypt the DB's, I have found references to SQL-TDE support in DP 6.1x platform support matrix doc, however the client is using DP 6.21 and there are no references to TDE in the support matrices from DP 6.2 onwards...any clues on why TDE is not even mentioned in the platform support matrices from DP6.2 to DP8?
This works in our production environment.
But HP - come on, folks, get your documentation complete. Please list the pre-reqs for using DP 8 with Exch 2013:
- .NET 3.5
- Visual C++ 2010 redistributable
(thanks, Bob Clark, for those two)
I am asking for some clarification on this, and will notify you as soon as I hear something
I actually found a lab case where this dependency was reported, and the documentation was supposed to have been updated. I wanted to look at the integration Guide to see if it made it in, but, that site is down right now (go figure). I'll try again tomorrow
Thanks for your response.
We tried the suggestion, but it made no difference. Even though the installation of DP had shown as successful, we decided to re-install it. This time it worked ok and we can access via the gui.
Hello I have problem with DP I have DP version 6.2 and I install locally windows server 2008 R2 eneterprise data protector client 7 but from DP server can not add cient then install 8 then version 7 but problem the same help me please
Since I don't know where these reports came from, it was hard for me to determine what would be meant by a Protection status of 'None", "Not Protected" or "Expired"
Maybe the best thing to do is to get some output about the media itself. At teh command prompt, run
omnimm -list_media [media label] -detail
omnimm -media_info [media label] -detail Do not include the [ ] marks
where [media label] can be either the DP media label, the Barcode label (if available) or teh Media ID, from teh INfo tab for the media
"Export" removes the sessions on that media from the Internal Database. If media is not exported, you will get an error when trying to import that teh media is already in the IDB. YOu would have to use 'Import Catalog' which does not do as good a job as Import
I have a related problem in my case the snapshot is not removed
Hello,
We have installed HP Data Protector 8.0 (Cell Manager) on physical machine.
Now we want to take filesystem backup of Windows 2000, but according to compatibility list of HPDP 8.0 it is not supporting Windows 2000.
So we found that HPDP 6.1X is the latest version supported by Windows 2000.
My question is,
Can we install HPDP 6.1X client on Windows 2000 machine with HPDP 8.0 Cell Manager on Windows 2008 R2 machine?
Does lower version of HPDP Client is supported with higher version of HPDP Cell Manager?
Please suggest. Thanks in advance.
Hello
Support for older agent versions
Wherever possible, Data Protector components on all clients in a Data Protector cell should be
upgraded to version 8.00 during the regular upgrade process. This ensures that customers can
benefit from the full feature set of Data Protector 8.00 on all systems in a cell.
However, due to the high demand, support for older agent versions has been extended. Disk Agent
and Media Agent components of an older Data Protector version (A.06.11, 6.20, or 7.00) are
supported in a 8.00 cell with the following constraints:
• Support is limited to the feature set of the older Data Protector version.
• If you are performing operations involving clients on different systems, all agents of the same
type (for example Media Agents) must be of the same version.
• Older Media Agent components are not supported in combination with NDMP servers.
• If one Data Protector component on a client is upgraded to 8.00, all other components have
to be upgraded to 8.00 as well.
If you have any problems establishing a connection with older agents, consider upgrading to 8.00
as the first resolution step.
Having a mixed environment is not officially supported. If something goes wrong on your 6.1 system, the Response center may not be able to help you
You will also be prone to getting strange warnings about Unknown Options
However, I know of a few people who have this kind of configuration, and it works