{"id":4379,"date":"2018-10-29T12:00:18","date_gmt":"2018-10-29T11:00:18","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=4379"},"modified":"2018-12-21T13:25:46","modified_gmt":"2018-12-21T12:25:46","slug":"data-protector-upgrade-paths","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2018\/10\/data-protector-upgrade-paths\/","title":{"rendered":"Data Protector Upgrade Paths"},"content":{"rendered":"<p><\/p>\r\n<p>Lately, we&#8217;ve been receiving more requests for potential Data Protector upgrade paths. This post includes a simple overview to guide you including intermediate steps necessary to upgrade to the latest version of the software.<\/p>\r\n<p><\/p>\r\n<p><\/p>\r\n<p>To reduce the amount of manual effort to a minimum you should always use the latest possible version allowed in the upgrade path (on Cell Manager and clients) before taking the next step, e.g. starting at 7.01, then upgrade to 9.00 and continue to 10.10.<\/p>\r\n<p>There might be some exceptions to this general rule depending on a lot of parameters i.e. new hardware, new operating systems, etc. Make sure to check the Release Notes and requirements of each (intermediate) version you plan to use as well as creating a offline backup and clean up the installation before you start.<\/p>\r\n<p><\/p>\r\n<p><\/p>\r\n<figure class=\"wp-block-image\">\r\n<div id=\"attachment_4381\" style=\"width: 650px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20.jpg\"><img aria-describedby=\"caption-attachment-4381\" loading=\"lazy\" class=\"wp-image-4381 size-large\" src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20-1024x576.jpg\" alt=\"DP_Upgrade_Paths\" width=\"640\" height=\"360\" srcset=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20-1024x576.jpg 1024w, https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20-150x84.jpg 150w, https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20-450x253.jpg 450w, https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20-768x432.jpg 768w, https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20.jpg 1280w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><\/a><p id=\"caption-attachment-4381\" class=\"wp-caption-text\">Last Update: 06. Dec. 2018<\/p><\/div>\r\n<figcaption><\/figcaption>\r\n<\/figure>\r\n<p><\/p>","protected":false},"excerpt":{"rendered":"<p>Lately, we&#8217;ve been receiving more requests for potential Data Protector upgrade paths. This post includes a simple overview to guide you including intermediate steps necessary to upgrade to the latest version of the software. To reduce the amount of manual effort to a minimum you should always use the latest possible version allowed in the [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[214],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":true,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-18D","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1365,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/ipc-invalid-packet-size\/","url_meta":{"origin":4379,"position":0},"title":"IPC Invalid Packet Size","date":"8. May 2013","format":false,"excerpt":"{:en}After the upgrade to DP 7.01 in some environments the rarley error IPC Invalid Packet Size has been seen while accessing a changer or tape device. The problem might be related to a slow name resolutuion on the media agent. The INET may run into a timeout before sending data\u2026","rel":"","context":"In &quot;HowTo&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":4379,"position":1},"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":4083,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/05\/sysbackup-oracle-12c\/","url_meta":{"origin":4379,"position":2},"title":"SYSBACKUP for Oracle 12c","date":"28. May 2018","format":false,"excerpt":"{:en}Starting with Oracle 12c three new administrative roles and users have been introduced to conform the principle of access to the least privilege. The users and roles named SYSBACKUP, SYSDG and SYSKM will be created when the database is created with their account in expired and locked status.\u00a0SYSBACKUP is used\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":4379,"position":3},"title":"Data Protector Migration Unix to other OS","date":"29. July 2011","format":false,"excerpt":"{:de}Ich kenne nicht viele gute Gr\u00fcnde warum man eine Data Protector Installation von HP-UX auf ein anderes Betriebssystem wechseln sollte,\u00a0dennoch gibt es viele Kunden die diesen Schritt gehen wollen und zum Beispiel auf Windows oder Linux wechseln;\u00a0meist noch verbunden mit einem Upgrade auf eine aktuelle Version von Data Protector.\u00a0Und hier\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2038,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/07\/data-protector-9-00-new\/","url_meta":{"origin":4379,"position":4},"title":"Data Protector 9 &#8211; Initial Release (Build 87)","date":"8. July 2014","format":false,"excerpt":"{:en}Data Protector 9.00 has been released. The new version delivers new features: \"Federated Catalyst\" and \"Non-Staged recovery using GRE for VMware vSphere\". For customers with a valid support contract, the new version can be downloaded here: http:\/\/support.openview.hp.com. Customers using an older version of Data Protector (Pre-8.XX) will require new licenses\u2026","rel":"","context":"In &quot;DP A.09.00&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":4379,"position":5},"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":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4379"}],"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\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=4379"}],"version-history":[{"count":26,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4379\/revisions"}],"predecessor-version":[{"id":4464,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/4379\/revisions\/4464"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=4379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=4379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=4379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}