{"id":1787,"date":"2014-01-15T12:00:16","date_gmt":"2014-01-15T11:00:16","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1787"},"modified":"2015-12-09T18:40:29","modified_gmt":"2015-12-09T17:40:29","slug":"advisory-dp-8-00-8-10","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2014\/01\/advisory-dp-8-00-8-10\/","title":{"rendered":"Advisory DP 8.00 \/ 8.10"},"content":{"rendered":"<p><b><u>Data Protector 8.10:<\/u><\/b> With Data Protector 8.10 it is very important to check name resolution before starting the installation. If it&#8217;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 &#8220;permission denied&#8221; 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.<\/p>\n<p><b><u>Update:<\/u><\/b> 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&#8221;. As a Workaround set locale to i.e. &#8216;en_gb-UTF-8&#8217; before starting the migration.<\/p>\n<p><b><u>Update:<\/u><\/b> 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 &#8216;To generate CA, client, and server certificates in the SG-CLUSTER environment&#8217;.<\/p>\n<p><b><u>Data Protector 8.00:<\/u><\/b> When using Granular Recovery Extension for Microsoft Exchange you may receive a &#8220;User does not have required roles&#8221; message. In this case the &#8220;Mailbox Import Export&#8221; role needs to be assigned directly to the GRE user. More details can be found here: <a href=\"http:\/\/support.openview.hp.com\/selfsolve\/document\/KM00482317\">http:\/\/support.openview.hp.com\/selfsolve\/document\/KM00482317<\/a> (HP Passport Account required).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Data Protector 8.10: With Data Protector 8.10 it is very important to check name resolution before starting the installation. If it&#8217;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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[24],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-sP","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1985,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/internal-error-launching-dp-gui\/","url_meta":{"origin":1787,"position":0},"title":"Internal error when launching DP GUI","date":"9. May 2014","format":false,"excerpt":"{:en}After a new installation of Data Protector and when the GUI is opened you might receive a \"Internal Error\" message. In this case the GUI cannot be used. It seems Windows 8.1 systems are involved. For more details and the solution please visit http:\/\/www.syncer.de\/?p=680. Thanks to Sebastian.{:} {:de}Nach einer einer\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1838,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/02\/current-patches-dp-8-0\/","url_meta":{"origin":1787,"position":1},"title":"Data Protector 8 &#8211; Patch Bundle 8.01","date":"3. February 2014","format":false,"excerpt":"{:en}On 2014\/01\/31 HP released patch bundle 8.01 for Linux, HP-UX and Windows. The update will fix many problems since version 8.00 was released, some were already addresses by SSP's - site specific patches. When looking at the patch description, about 100 fixes and some new features (support for vSphere 5.1\u2026","rel":"","context":"In &quot;DP A.08.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1169,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/10\/dp-7-01-remote-installation-linux-working\/","url_meta":{"origin":1787,"position":2},"title":"DP 7.01 remote installation Linux not working","date":"1. October 2012","format":false,"excerpt":"{:en}With Data Protector 7.01 there might be a problem when doing a remote installation of a Linux Client with Kernel 3 (i.e. SLES 11 SP2). In the GUI you might receive an error that the client is not supportet. This is a known problem and was fixed in previous versions\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":1787,"position":3},"title":"Installation order of Patches","date":"3. June 2013","format":false,"excerpt":"{:de}Immer wieder stellt sich die Frage in welcher Reihenfolge die Patches f\u00fcr Data Protector installiert werden. Zwischen den einzelnen Patches ergeben sich Abh\u00e4ngigkeiten, welche man in den Beschreibungsdateien zum Patch nachlesen kann; diese m\u00fcssen bei der Installation eingehalten werden. Generell gilt folgende Reihenfolge f\u00fcr die Installation: sofern vorhanden: Patchbundle, Core,\u2026","rel":"","context":"In &quot;History&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":842,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/01\/advisory-data-protector-org\/","url_meta":{"origin":1787,"position":4},"title":"Advisory Data-Protector.org","date":"11. January 2012","format":false,"excerpt":"{:en}Different customers reported about problems with multipath devices in DP 6.21. The configuration of the multipath devices is no longer possible. The problem is with the GUI only, as backups run as expected. Following workarounds are possible: - Open a call and request hotfix QCCR2A35525. - Downgrade to DP 6.2\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1799,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/03\/updated-support-matrices-data-protector-8-10-8-00-7-03\/","url_meta":{"origin":1787,"position":5},"title":"Updated support matrices for Data Protector 8.10, 8.00 and 7.03","date":"25. March 2014","format":false,"excerpt":"{:en}Update: On 2014\/03\/25 the support matrices for Data Protector 8.10, 8.01 and 7.03 were updated; please review. Update: On 2014\/02\/25 the support matrices for Data Protector 8.10, 8.00 and 7.03 were updated and includes fixes from the January matrices The support matrices for Data Protector 8.10, 8.00 and 7.03 were\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1787"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=1787"}],"version-history":[{"count":7,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1787\/revisions"}],"predecessor-version":[{"id":2606,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1787\/revisions\/2606"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}