{"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\/de\/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> F\u00fcr die Data Protector 8.10 ist es besonders wichtig die Namensaufl\u00f6sung zu kontrollieren. L\u00e4sst sich der Cell Server nicht mit dem FQDN (und short und reverse) aufl\u00f6sen, so sieht man beim \u00d6ffnen der GUI nur eine Anmeldemaske (LDAP Anmeldung als alternative Anmeldem\u00f6glichkeit) und danach die Meldung &#8222;Permission denied&#8220;. Die funktionsf\u00e4hige Namensaufl\u00f6sung wird auch ausdr\u00fccklich als Voraussetzung f\u00fcr DP 8.10 aufgelistet. Falls die Installation von DP 8.10 ohne funktionierende Namensaufl\u00f6sung durchgef\u00fchrt wurde, so ist derzeit nur eine Neuinstallation nach der Fehlerbehebung m\u00f6glich; ein neu generiertes Zertifikats wurde nicht akzeptiert. Hintergrund: Mit DP 8.10 werden Zertifikate f\u00fcr den Zugriff auf die GUI verwendet, das erstellte Zertifikat muss beim ersten Aufrufen der GUI akzeptiert werden. Wenn der Systemname abweichend vom Zertifikatsnamen ist, so ist eine Anmeldung nicht m\u00f6glich, da TLS nur mit FQDN arbeitet.<\/p>\n<p><b><u>Update:<\/u><\/b> F\u00fcr den Fall, dass der Data Protector auf einem deutschen bzw. nicht englischem Linux System installiert wird, kann die Erstellung der Zertifikate fehlschlagen. Grund hierf\u00fcr ist, dass die R\u00fcckgabewerte auf Englisch erwartet werden. Als Workaround setzt man die locale vor dem Upgrade auf zum Beispiel &#8218;en_gb-UTF-8&#8216;.<\/p>\n<p><b><u>Update:<\/u><\/b> F\u00fcr den Fall, dass der Data Protector im Cluster l\u00e4uft, wird unter Umst\u00e4nden das Zertifikat f\u00fcr den physikalischen Host, statt dem virtuellen Namen ausgestellt. Hier gibt es die M\u00f6glichkeit mit dem Perl Programm omnigencert.pl ein Zertifikat f\u00fcr den virtuellen Namen des Clusters auszustellen. Die genaue Anleitung findet man in der Hilfe bei der Suche nach &#8218;To generate CA, client, and server certificates in the SG-CLUSTER environment&#8216;.<\/p>\n<p><b><u>Data Protector 8.00:<\/u><\/b> Beim Verwenden von Granular Recovery Extension for Microsoft Exchange kann es zu &#8222;User does not have required roles&#8220; Meldungen kommen. Grund hierf\u00fcr ist dass die &#8222;Mailbox Import Export&#8220; Rolle direkt dem GRE Benutzer zugeordnet werden muss. Mehr Details k\u00f6nnen unter <a href=\"http:\/\/support.openview.hp.com\/selfsolve\/document\/KM00482317\">http:\/\/support.openview.hp.com\/selfsolve\/document\/KM00482317<\/a> (HP Passport Account ben\u00f6tigt) nachgelesen werden.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Data Protector 8.10: F\u00fcr die Data Protector 8.10 ist es besonders wichtig die Namensaufl\u00f6sung zu kontrollieren. L\u00e4sst sich der Cell Server nicht mit dem FQDN (und short und reverse) aufl\u00f6sen, so sieht man beim \u00d6ffnen der GUI nur eine Anmeldemaske (LDAP Anmeldung als alternative Anmeldem\u00f6glichkeit) und danach die Meldung &#8222;Permission denied&#8220;. Die funktionsf\u00e4hige Namensaufl\u00f6sung wird [&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":"de","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":1799,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/updated-support-matrices-data-protector-8-10-8-00-7-03\/","url_meta":{"origin":1787,"position":0},"title":"Updated support matrices for Data Protector 8.10, 8.00 and 7.03","date":"25. M\u00e4rz 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":[]},{"id":1743,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/12\/brick-version-v1-10-support-dp-8-10-linuxwindows-browser\/","url_meta":{"origin":1787,"position":1},"title":"BRICK &#8211; new Version v1.10 with support for DP 8.10, Linux\/Windows, different browser","date":"29. Dezember 2013","format":false,"excerpt":"{:en}BRICK - the new version 1.10 has been released!!! Continue to read here: https:\/\/www.data-protector.org\/wordpress\/brick\/. Update 2013\/12\/29: the new version v1.10 has been released. For more information please refer to the change log; especially the support for Data Protector 8.10, Linux\/Windows and the browser of your choice was added. Please use\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1838,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/02\/current-patches-dp-8-0\/","url_meta":{"origin":1787,"position":2},"title":"Data Protector 8 &#8211; Patch Bundle 8.01","date":"3. Februar 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":1849,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/02\/beta-omnispeed-version-2-0\/","url_meta":{"origin":1787,"position":3},"title":"BETA &#8211; omnispeed version 2.0","date":"12. Februar 2014","format":false,"excerpt":"{:en}BETA testers wanted. Omnispeed has been established as tool to test the performance of backups, copy jobs and restores. Due to limitations of the current version (language and regional settings) and with the introduction of Data Protector 8.0, it was necessary to modify current version. Prior releasing the new version\u2026","rel":"","context":"In &quot;SCD&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1710,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/data-protector-8-10-whats-new\/","url_meta":{"origin":1787,"position":4},"title":"Data Protector 8.10 available &#8211; whats new?","date":"7. Januar 2014","format":false,"excerpt":"{:en}Data Protector 8.10 has been released. The new version delivers some new features, my favorites are the new advanced scheduler and the file-system backup, which can be resumed. For customers with a valid support contract, the new version can be downloaded here: http:\/\/support.openview.hp.com. With Data Protector 8.1 new licenses are\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2063,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/07\/cell-console-patch-dp-8-10-based-patch-bundle-8-12\/","url_meta":{"origin":1787,"position":5},"title":"Data Protector 8 &#8211; GR Patches 8.10","date":"24. Juli 2014","format":false,"excerpt":"{:en}On 2014\/07\/23 HP released a cell console patch for Linux, HP-UX and Windows. The patch bundle 8.12 is required as prerequisite. It is strongly recommended to read the full description of the bundle. If you own a valid support contract you can download the patches from http:\/\/support.openview.hp.com\/selfsolve\/patches. Access requires the\u2026","rel":"","context":"In &quot;DP A.08.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1787"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/comments?post=1787"}],"version-history":[{"count":7,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1787\/revisions"}],"predecessor-version":[{"id":2606,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1787\/revisions\/2606"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1787"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1787"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}