Category Archives: Advisory

Data Protector 8.10: With Data Protector 8.10 it is very important to check name resolution before starting the installation. If it’s not possible to resolve the FQDN of the cell server (of course short and revers too), a login prompt will appear when opening the GUI (this is the LDAP logon dialog, which is an additional feature in DP 8.10) and a “permission denied” message afterwards. In documentation it is listed that a working name resolution is a requirement for DP 8.10. If the installation was done without working name resolution for the cell server, a new installation has to be done after name resolution was fixed; a newly generated certificate was not accepted by the GUI. Additional information: With DP 8.10 certificates are used locally to access the GUI, you will be prompted to accept the certificate when launching the GUI for the first time after the installation. In case your system name is different from the name in the certificate the local logon will fail as TLS will work with FQDN only.

Update: If the Cell Server is installed on a German or Non-English Linux system, the generated certificate might be wrong or will not be generated. This happens as the return values are expected to be in English, which is not true when locale is not set to English”. As a Workaround set locale to i.e. ‘en_gb-UTF-8’ before starting the migration.

Update: If the Cell Server is installed in a cluster environment, the certificate might be issued for the physical host, instead of virtual name. With the Perl program omnigencert.pl it is possible to generate a certificate using the virtual name of the cluster. For more details refer to help and search for ‘To generate CA, client, and server certificates in the SG-CLUSTER environment’.

Data Protector 8.00: When using Granular Recovery Extension for Microsoft Exchange you may receive a “User does not have required roles” message. In this case the “Mailbox Import Export” role needs to be assigned directly to the GRE user. More details can be found here: http://support.openview.hp.com/selfsolve/document/KM00482317 (HP Passport Account required).

With document ID c03823106 on 2013/07/10 an advisory for HP Data Protector 6.21, 7.01, 8.00 was released, describing a problem when VSS is used for the backups. In some cases it could happen, that the VSS snapshot is corrupted and Data Protector backed up the corrupted snapshot.

As the root cause is the VSS framework from Microsoft, the fix to solve the problem is delivered by Microsoft – http://support.microsoft.com/kb/2748349. Windows 7 SP1 and Windows 2008 R2 SP1 already contain this fix.

The complete advisory can be read here: http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03823106-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

With document ID c03753986 on 2013/05/06 an advisory for HP Data Protector 6.11, 6.20, 6.21, 7.0 and 7.01 was released, describing a problem for restores of SAP data files and the file size is different from the SAP data file. When the omnirc parameter OB2SAPALIGN was used on Unix a possible read error is not reported during the backup and in case of restore you may receive an error and are unable to recover the SAP data file (silent data loss).

As a workaround disable the omnirc variable OB2SAPALIGN=0 on the SAP client. The problem will be solved with the next release of HP Data Protector.

The complete advisory can be read here: http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03753986-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken