{"id":165,"date":"2010-08-18T16:37:05","date_gmt":"2010-08-18T14:37:05","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=165"},"modified":"2015-12-10T11:19:02","modified_gmt":"2015-12-10T10:19:02","slug":"unattended-installation-data-protector","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/08\/unattended-installation-data-protector\/","title":{"rendered":"Unattended Installation Data Protector"},"content":{"rendered":"<p>Im Zeitalter von VMware, HP Blade Umgebungen, Altiris und Co. werden Server in der Regel nicht mehr manuell installiert, sondern unattended. Data Protector bietet ja verschiedene M\u00f6glichkeiten einen Server mit der Client Software zu installieren (GUI, Manuell, msiexec, csetup). Wenn ich es aber richtig unattended haben will dann hilft vielleicht folgendes Skript&#8230; Ich betrachte hier mal nur Windows (i386 und x8664, kein Itanium), UNIX (Ignite) und Linux bieten ja eigene \/ andere M\u00f6glichkeiten<\/p>\n<p>Am einfachsten finde ich den Weg hier mit csetup, der Aufruf ist recht simple, wichtig ist der <code>ADDLOCAL<\/code> Teil, den ich hier nur mal mit DA und AutoDR angegeben habe, es lassen sich aber auch SAP, Oracle, GUI, usw. damit installieren. Eine Variabel nutze ich hier nicht, mit <code>INSTALLDIR=&lt;Pfad&gt;<\/code> kann man den Default Installationsort vom Data Protector Client \u00e4ndern.<\/p>\n<p>Der generelle Aufruf sieht so aus: <code>csetup -quiet INSTALLATIONTYPE=Client ADDLOCAL=core,da,autodr CELLNAME=&lt;cellserver name - fqdn&gt; PORT=5555<\/code><\/p>\n<p>Und hier mal ein Besipiel Skript, Teile in &lt;&gt; einfach entsprechend auswechseln:<br \/>\n<code><br \/>\n@echo off<br \/>\necho Generating environment<br \/>\nset currentdir=%~dp0<br \/>\nmkdir %temp%\\DP<br \/>\ncd %temp%\\DP<\/code><br \/>\n<code><br \/>\necho checking OS version<br \/>\nset RegQry=HKLM\\Hardware\\Description\\System\\CentralProcessor\\0<br \/>\nREG.exe Query %RegQry% &gt; temp.txt<br \/>\nFind \/i \"x86\" &lt; temp.txt &gt; temp1.txt<br \/>\nif %ERRORLEVEL% == 0 (<br \/>\n\u00a0 ECHO OS is 32 BIT<br \/>\n\u00a0 set NETUSECOMMAND=\\\\&lt;cellserver name - fqdn&gt;\\omniback \/user:&lt;servername | domain&gt;\\user password<br \/>\n\u00a0 set INSTALL=i386<br \/>\n) ELSE (<br \/>\n\u00a0 ECHO OS is 64 BIT<br \/>\n\u00a0 set NETUSECOMMAND=\\\\&lt;cellserver name - fqdn&gt;\\omniback \/user:&lt;servername | domain&gt;\\user password<br \/>\n\u00a0 set INSTALL=x8664<br \/>\n)<\/code><br \/>\n<code><br \/>\necho connecting drive and starting installation<br \/>\nnet use Z: %NETUSECOMMAND% &gt; NUL<br \/>\nZ:<br \/>\ncd \\<br \/>\ncd %INSTALL%<\/code><br \/>\n<code><br \/>\ncsetup -quiet INSTALLATIONTYPE=Client ADDLOCAL=core,da,autodr CELLNAME=&lt;cellserver name - fqdn&gt; PORT=5555<br \/>\n<\/code><\/p>\n<p><code>echo Cleanup<br \/>\ncd %temp%\\DP<br \/>\ndel temp.txt<br \/>\ndel temp1.txt<br \/>\ncd %temp%<br \/>\nrmdir %temp%\\DP<br \/>\nnet use Z: \/d &gt; NUL<br \/>\ncd %currentdir%<br \/>\necho Finished<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Im Zeitalter von VMware, HP Blade Umgebungen, Altiris und Co. werden Server in der Regel nicht mehr manuell installiert, sondern unattended. Data Protector bietet ja verschiedene M\u00f6glichkeiten einen Server mit der Client Software zu installieren (GUI, Manuell, msiexec, csetup). Wenn ich es aber richtig unattended haben will dann hilft vielleicht folgendes Skript&#8230; Ich betrachte hier [&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":[11],"tags":[78],"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-2F","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":165,"position":0},"title":"Installation order of Patches","date":"3. Juni 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":3589,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2017\/05\/data-protector-9-gr-patches-9-09-build-115\/","url_meta":{"origin":165,"position":1},"title":"Data Protector 9 \u2013 GR Patches 9.09 (Build 115)","date":"31. Mai 2017","format":false,"excerpt":"{:en}The General Release Patches\u00a0A.09.09 (Build 115) for Data Protector 9 has been released on May 31, 2017. The 115 GR Patches must be installed on top of the A.09.09 Patch Bundle. It is recommended to install all the GR Patches as a group regardless if the updated components are used\u2026","rel":"","context":"In &quot;DP A.09.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1097,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/08\/data-protector-sles-11-sp2\/","url_meta":{"origin":165,"position":2},"title":"Data Protector and SLES 11 SP2","date":"29. August 2012","format":false,"excerpt":"{:en}Since the latest patches for Data Protector (621, 701) the kernel version 3 for Linux is supported to install a new client using installation server. In general there shouldn't be a problem during the installation, however when you receive following error message (i.e. for OpenSuse or SLES 11 SP2): Unsupported\u2026","rel":"","context":"In &quot;Advisory&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":165,"position":3},"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":[]},{"id":3591,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2017\/08\/data-protector-9-gr-patches-9-09-build-116\/","url_meta":{"origin":165,"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":2270,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/01\/data-protector-client-debian-based-systems\/","url_meta":{"origin":165,"position":5},"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":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/165"}],"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=165"}],"version-history":[{"count":6,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/165\/revisions"}],"predecessor-version":[{"id":2753,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/165\/revisions\/2753"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}