In order to install the Data Protector client software on Linux based systems and on HP-UX, you need to have a server with the installation server package installed. With an installation server you are able to distribute the software onto new clients or to upgrade existing clients (push installation). I use a virtual machine with a basic installation and no graphical interface in these cases. The installation server is supported on RedHat, CentOS, Oracle Enterprise Linux and SUSE Linux Enterprise Server (details and version information can be found in matrix: Platform_Integrtn_SptMtx.pdf). With the documentation below I show you how to install or upgrade the Data Protector Linux Installation Server. This includes the removal of an older major version and will not take more than five minutes in total.<\/p>\n
Remove older Data Protector version:<\/b><\/p>\n Comment: This is not the recommended way to uninstall Data Protector, but the fastest method. Keep in mind that Data Protector site specific patches or other hotfixes may not have been installed with the “OB2” string in the package description.\n<\/p>\n Install new Data Protector version (Installation Server only):<\/b><\/p>\n * or any other folder with sufficient space Register Installation Server in Data Protector Cell:<\/b><\/p>\n * This step is required only if the server was already an installation server Create public\/private rsa key pair:<\/b><\/p>\n * Answer the questions to generate the “key pair” In order to install the Data Protector client software on Linux based systems and on HP-UX, you need to have a server with the installation server package installed. With an installation server you are able to distribute the software onto new clients or to upgrade existing clients (push installation). I use a virtual machine with […]<\/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":[],"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-A5","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":4128,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/05\/data-protector-10-patch-bundle-a-10-04-build-182\/","url_meta":{"origin":2237,"position":0},"title":"Data Protector 10 \u2013 Patch Bundle A.10.04 (Build 182)","date":"23. May 2018","format":false,"excerpt":"{:en}The Patch Bundle A.10.04 (Build 182) for Data Protector 10 has been released on May 22, 2018. Data Protector A.10.03 was released as a full install therefore the cumulative patch 10.04 can only be installed on top of A.10.03. A direct upgrade from A.10.00, A.10.01 or A.10.02 is not possible!\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3517,"url":"https:\/\/www.data-protector.org\/wordpress\/2017\/12\/data-protector-10-patch-bundle-a-10-02-build-308\/","url_meta":{"origin":2237,"position":1},"title":"Data Protector 10 \u2013 Patch Bundle A.10.02 (Build 308)","date":"7. December 2017","format":false,"excerpt":"{:en}The Patch Bundle A.10.02 (Build 308) for Data Protector 10 has been released on December 7, 2017. The cumulative patch can be installed on top of A.10.00\u00a0or any later Patch Bundle or General Release patch. It is recommended to install it on all Installation Servers (IS) and the Cell Managers\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3514,"url":"https:\/\/www.data-protector.org\/wordpress\/2017\/09\/data-protector-10-patch-bundle-a-10-01-build-307\/","url_meta":{"origin":2237,"position":2},"title":"Data Protector 10 \u2013 Patch Bundle A.10.01 (Build 307)","date":"28. September 2017","format":false,"excerpt":"{:en}The Patch Bundle A.10.01 (Build 307) for Data Protector 10 has been released on September 28, 2017. This first cumulative patch can be installed on top of A.10.00. It is recommended to install it on all Installation Servers (IS) and the Cell Managers (CM). Then push the new packages from\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1097,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/08\/data-protector-sles-11-sp2\/","url_meta":{"origin":2237,"position":3},"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 "Advisory"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3581,"url":"https:\/\/www.data-protector.org\/wordpress\/2017\/03\/data-protector-9-patch-bundle-9-09-build-114\/","url_meta":{"origin":2237,"position":4},"title":"Data Protector 9 \u2013 Patch Bundle 9.09 (Build 114)","date":"30. March 2017","format":false,"excerpt":"{:en}The Patch Bundle A.09.09 (Build 114) for Data Protector 9 has been released on March 30, 2017. The cumulative patch can be installed on top of A.09.00 or any later Patch Bundle or General Release patch. It is recommended to install it on all Installation Servers (IS) and the Cell\u2026","rel":"","context":"In "DP A.09.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3937,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/04\/data-protector-9-gr-patches-9-09-build-117\/","url_meta":{"origin":2237,"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 "DP A.09.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2237"}],"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=2237"}],"version-history":[{"count":17,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2237\/revisions"}],"predecessor-version":[{"id":2795,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/2237\/revisions\/2795"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=2237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=2237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=2237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\r\ncp \/opt\/omni\/.omnirc \/tmp\/.omnirc.sav\r\nrpm -qa | grep -i ob2 > \/tmp\/removeOB2\r\nfor PACKAGE in `cat \/tmp\/removeOB2`; do rpm -e $PACKAGE --nodeps --noscripts; done;\r\ncp \/etc\/services \/tmp\/services.bak\r\ncat \/etc\/services | sed -e \"s\/omni\/\\#omni\/\" > \/tmp\/services.new\r\ncp \/tmp\/services.new \/etc\/services\r\nrm \/etc\/xinetd.d\/omni \r\nrm -r \/etc\/opt\/omni\r\nrm -r \/opt\/omni\r\nrm -r \/var\/opt\/omni\r\nrm \/tmp\/removeOB2\r\nrm \/tmp\/services.new\r\n<\/pre>\n
\r\nmkdir \/dpinstall (*)\r\nmkdir \/dpinstall\/dp9\r\nmkdir \/dpinstall\/dp9pb\r\ncopy ISO file to \/dpinstall (**) \r\ncopy patch bundle file to \/dpinstall (***)\r\nmount -o loop \/dpinstall\/TD586-15021.iso \/dpinstall\/dp9\r\n\/dpinstall\/dp9\/LOCAL_INSTALL\/omnisetup.sh -IS\r\numount \/dpinstall\/dp9\r\ntar -xvf DPLNXBDL_00902.tar -C \/dpinstall\/dp9pb\/\r\ncd \/dpinstall\/dp9pb\r\n.\/omnisetup.sh -bundleadd b902\r\ncd \/\r\nrm -r \/dpinstall\r\ncp \/tmp\/.omnirc.sav \/opt\/omni\/.omnirc (****)\r\n<\/pre>\n
\n** e.g. TD586-15021.iso – Data Protector 9.00 Linux – use winscp to copy the file
\n*** e.g. DPLNXBDL_00902.tar – Data Protector 9.02 Linux – use winscp to copy the file
\n**** if file exists – see remove older version of Data Protector
\n
\nIn the example it is assumed that a patch bundle needs to be installed in addition. If no patch bundle is available the steps 3, 5, 9, 10 and 11 are not required. After the installation it is recommend to check the content of the file .omnirc<\/code>; at least the variable OB2_SSH_ENABLED=1<\/code> in file \/opt\/omni\/.omnirc<\/code> is required in order to distribute new clients using Data Protector GUI. If the file does not exist you can create it from template – cp \/opt\/omni\/.omnirc.TMPL \/opt\/omni\/.omnirc<\/code>. If additional updates are available copy the patches onto the server and decompress using command tar<\/code>. A rpm package and text file will be generated. Within the text files the command to install the patch can be found. Please keep in mind, Data Protector patches will be installed using a special order; for details see https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/<\/a>.\n<\/p>\n\r\nomnicc -export_is <installation server> (*)\r\nomnicc -import_is <installation server> (**) \r\n<\/pre>\n
\n** Use the name of the server (FQDN) for “installation server”
\n
\nIf this installation server was already used in the past to install the Data Protector client software, you now can use it to upgrade your existing client using the Data Protector GUI. If this installation server is your first installation server you need to configure SSH based authentication first.\n<\/p>\n\r\nssh-keygen (*)\r\nssh <client - short name> (**) \r\nssh <client - FQDN name> (**) \r\nssh <client - IP address> (**) \r\nAdd public key (***)\r\n<\/pre>\n
\n** You can cancel the login once you accepted the host key for the client
\n*** Use ssh<\/code> to login into the new client and add the public key from the installation server (cat \/root\/.ssh\/id_rsa.pub<\/code>) into the file \/root\/.ssh\/authorized_keys<\/code>
\n
\nIt is assumed that defaults will be used when using the command ssh-keygen<\/code>. Furthermore it is assumed that all defaults were used for the SSH configuration and paths.<\/p>\n","protected":false},"excerpt":{"rendered":"