{"id":1097,"date":"2012-08-29T10:31:34","date_gmt":"2012-08-29T08:31:34","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1097"},"modified":"2015-12-09T20:47:29","modified_gmt":"2015-12-09T19:47:29","slug":"data-protector-sles-11-sp2","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/08\/data-protector-sles-11-sp2\/","title":{"rendered":"Data Protector and SLES 11 SP2"},"content":{"rendered":"<p>Sp\u00e4testens seit den letzten Patches f\u00fcr Data Protector (621, 701) sollte die Kernel Version 3 f\u00fcr Linux unterst\u00fctzt sein um einen neuen Client \u00fcber den Installation Server zu installieren. Das sollte auch prinzipiell funktionieren, wenn aber dennoch die Fehlermeldung ausgeben wird (z.B. bei OpenSuse und SLES 11 SP2): <i><b>Unsupported architecture\/OS type (Linux CLIENT 3.1.9-1.4-desktop #1 SMP PREEMT &#8230;) Skipping Client!<\/b><\/i>, dann gibt es daf\u00fcr 2 Workarounds und 1 L\u00f6sung. Workaround 1: lokale Installation von core.rpm und da.rpm auf dem Client (die Packages kann man aus dem Installation Server extrahieren), Workaround 2: die Datei \/etc\/os-release nach \/etc\/novell-release auf dem zu installierenden Client kopieren und die Installation \u00fcber die GUI starten. Die L\u00f6sung w\u00e4re der Hotfix von HP (QCCR Nummer poste ich sobald der Fix verf\u00fcgbar ist).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sp\u00e4testens seit den letzten Patches f\u00fcr Data Protector (621, 701) sollte die Kernel Version 3 f\u00fcr Linux unterst\u00fctzt sein um einen neuen Client \u00fcber den Installation Server zu installieren. Das sollte auch prinzipiell funktionieren, wenn aber dennoch die Fehlermeldung ausgeben wird (z.B. bei OpenSuse und SLES 11 SP2): Unsupported architecture\/OS type (Linux CLIENT 3.1.9-1.4-desktop #1 [&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":[148,149,150],"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-hH","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1169,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/10\/dp-7-01-remote-installation-linux-working\/","url_meta":{"origin":1097,"position":0},"title":"DP 7.01 remote installation Linux not working","date":"1. Oktober 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":2270,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/01\/data-protector-client-debian-based-systems\/","url_meta":{"origin":1097,"position":1},"title":"Data Protector client on Debian based systems","date":"27. Januar 2015","format":false,"excerpt":"{:en} If you need to install the Data Protector client software on a Debian based system, you will recognize no derivate is listed in the support matrix as supported version and the Debian Linux 6.0 (x64) and 7.0 (x64), and Ubuntu 12.x (x64) are supported only. However, if you require\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1787,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/advisory-dp-8-00-8-10\/","url_meta":{"origin":1097,"position":2},"title":"Advisory DP 8.00 \/ 8.10","date":"15. Januar 2014","format":false,"excerpt":"{:en}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\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":230,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/11\/cannot-create-integration-backups-when-patch-dpwin_00483-is-installed\/","url_meta":{"origin":1097,"position":3},"title":"Cannot Create Integration Backups when Patch DPWIN_00483 is installed","date":"21. November 2010","format":false,"excerpt":"{:en}Once you installed the patch DPWIN_00483 (VEPA patch) you are no longer able to create new integration backups (Exchange, SQL, ...). Withhin GUI you are not able to browse for instances. The bug comes from changed manager.exe through patch DPWIN_00483. As a workaround you may use the JAVA GUI where\u2026","rel":"","context":"In &quot;Bugs&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3591,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2017\/08\/data-protector-9-gr-patches-9-09-build-116\/","url_meta":{"origin":1097,"position":4},"title":"Data Protector 9 \u2013 GR Patches 9.09 (Build 116)","date":"8. August 2017","format":false,"excerpt":"{:en}The General Release Patches\u00a0A.09.09 (Build 116) for Data Protector 9 has been released on August 8, 2017. The 116 GR Patches must be installed on top of the 115 GR Patches (which requires Patch Bundle 9.09). It is recommended to install all the GR Patches as a group regardless if\u2026","rel":"","context":"In &quot;DP A.09.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3937,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/04\/data-protector-9-gr-patches-9-09-build-117\/","url_meta":{"origin":1097,"position":5},"title":"Data Protector 9 \u2013 GR Patches 9.09 (Build 117)","date":"5. April 2018","format":false,"excerpt":"{:en}The General Release Patches\u00a0A.09.09 (Build 117) for Data Protector 9 has been released on April 4, 2018. The 117 GR Patches must be installed on top of the 115 and 116 GR Patches (which requires Patch Bundle 9.09). It is recommended to install all the GR Patches as a group\u2026","rel":"","context":"In &quot;DP A.09.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\/1097"}],"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=1097"}],"version-history":[{"count":6,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1097\/revisions"}],"predecessor-version":[{"id":2689,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1097\/revisions\/2689"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1097"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1097"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1097"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}