{"id":1160,"date":"2012-09-19T10:59:39","date_gmt":"2012-09-19T08:59:39","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1160"},"modified":"2015-12-10T19:43:30","modified_gmt":"2015-12-10T18:43:30","slug":"recover-cell-server-reviewed","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2012\/09\/recover-cell-server-reviewed\/","title":{"rendered":"Recover Cell Server &#8211; Reviewed"},"content":{"rendered":"<p>In previous posts it is documented how to recover a server using Enhanced Automated Disaster Recovery Option. Tis applies to the Cell Server too, as this server might be the most important server in a case of a disaster. For the cell server there are several options available to do a fast recovery. The following steps apply to cell server for all supported operating systems and the steps are only 1 possible way for recovery.<\/p>\n<p>The most important information when a recovery of the cell server is required will be the information on which media is the backup of the internal database. With 2 settings you make sure the information is available when needed (if copied off the cell server per scheduled task). First you have to edit the file <code>rdmserver.ini<\/code> and to enable the parameter <code>archiving=1<\/code>. In this case DP will write the information regarding the backup of IDB to an additional file. Second step is to change file <code>global<\/code> and to enable the parameter <code>RecoveryIndexDir=PathToBackupDir<\/code>. After saving both files you need to restart the DP services. With the first backup of the IDB information regarding the backup is written to <code>obrindex.dat<\/code>.<\/p>\n<p>In this file you now have the information which media was used during the backup and also some additional information regarding the drive used during the backup.<\/p>\n<p><img loading=\"lazy\" src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2010\/11\/obrindex.dat_.jpg\" alt=\"obrindex.dat\" width=\"537\" height=\"107\" \/><\/p>\n<p>An additional Step to prepare for DR is the export of the devices. This can be done with the tool omnidownload. The command will generate some text files to be used to create devices in case of disaster using the command omniupload. Of course you can use the tool &#8220;SaveDevices&#8221; to automate this task (can be found in download section).<\/p>\n<p>In case of a disaster in general you can follow the steps below:<\/p>\n<ul>\n<li>Change \/ repair defect hardware<\/li>\n<li>Install operating system<\/li>\n<li>Installation Data Protector as cell server<\/li>\n<li>Create new devices to be able to import IDB into IDB<\/li>\n<li>Import media with IDB backup<\/li>\n<li>Restore of IDB<\/li>\n<li>Restore of all other settings<\/li>\n<\/ul>\n<p>As written above these steps are only one way to recover the cell server. In the articles EADR W2K and Recover Cell Server additional ways using SRD \/ omniiso are described.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In previous posts it is documented how to recover a server using Enhanced Automated Disaster Recovery Option. Tis applies to the Cell Server too, as this server might be the most important server in a case of a disaster. For the cell server there are several options available to do a fast recovery. The following [&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":[86,156],"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-iI","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":313,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/01\/eadr-mit-windows-2008-r2\/","url_meta":{"origin":1160,"position":0},"title":"EADR with Windows 2008 R2","date":"21. January 2011","format":false,"excerpt":"{:de}In einen fr\u00fcheren Artikel hatte ich \u00fcber die Wiederherstellung eines Windows 2003 Servers mit Data Protector berichtet. Nachdem Windows 2008 auch immer mehr in Rechenzentren betrieben wird zeige ich nachfolgend die Wiederherstellung eines Windows 2008 R2 Servers mit Data Protector und der Enhanced Automated Disaster Recovery Funktion. Vorbereitung: In der\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2190,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/eadr-tape-block-size\/","url_meta":{"origin":1160,"position":1},"title":"EADR and Tape Block Size","date":"1. January 2015","format":false,"excerpt":"{:en}In older articles I often wrote about Bare Metal Recovery, a feature included in Data Protector without any additional costs and called Enhanced Automated Disaster Recovery (EADR) - see https:\/\/www.data-protector.org\/wordpress\/?s=eadr. To recover the Cell Server (see link) I always told to use tape devices with a block size of 64K.\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":388,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/03\/savedevices-omnidownload\/","url_meta":{"origin":1160,"position":2},"title":"SaveDevices &#8211; omnidownload","date":"16. March 2011","format":false,"excerpt":"{:de}Im Rahmen des Disaster Recovery f\u00fcr den Cell Server empfiehlt es sich neben der obrindex.dat - siehe Recover Cell Server auch die Libraries und Devices herunterzuladen, um sie im Bedarfsfall wieder schnell generieren zu k\u00f6nnen. Daf\u00fcr habe ich das kleine Tool SaveDevices geschrieben, welches die Konfiguration in Text Dateien ablegt.\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":1160,"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":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":1160,"position":4},"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":3103,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/05\/data-protector-9-06-patches-build-108\/","url_meta":{"origin":1160,"position":5},"title":"Data Protector 9 &#8211; GR Patches 9.06 (Build 108)","date":"24. May 2016","format":false,"excerpt":"{:en}On 2016\/05\/24 HPE released new patches for Linux, Windows and HP-UX (build 108). This is not the patch bundle 9.07 (expected in June timeframe). As a requirement you need to have Patch Bundle 9.06 installed. It is strongly recommended to read the full description of each patch. If you own\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\/wp-json\/wp\/v2\/posts\/1160"}],"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=1160"}],"version-history":[{"count":8,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1160\/revisions"}],"predecessor-version":[{"id":2841,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1160\/revisions\/2841"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}