{"id":1987,"date":"2014-05-23T08:17:01","date_gmt":"2014-05-23T07:17:01","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1987"},"modified":"2015-12-09T18:05:23","modified_gmt":"2015-12-09T17:05:23","slug":"distribute-omnirc-file","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/","title":{"rendered":"Distribute omnirc File"},"content":{"rendered":"<p>\nYou know Data Protector? So you know that the modification of parameter for Data Protector is done in file global and in file omnirc. The file global is maintained on the Cell Server directly, but the file omnirc (Linux\/HP-UX: <code>\/opt\/omni<\/code>, Windows 2008 <code>C:\\programdata\\omniback<\/code>) has to be maintained on each client individually. The Data Protector admin often maintains one version on the Cell Server and distribute the modified file manually to each individual client. That&#8217;s the case, because no distribution mechanism exist for the file omnirc, at least in the past.<\/p>\n<p>With Data Protector 8.11 there is a new way to modify omnirc values for the clients, using the command <code>util_cmd<\/code>.<\/p>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px\">\r\nutil_cmd -setomnirc &lt;hostname&gt; &lt;name&gt; [&lt;value&gt;]\r\nutil_cmd \u2013getomnirc &lt;hostname&gt; &lt;name&gt;\r\n\r\nname      \u2013 the name of the environment variable written in DP omnirc file.\r\nhostname  \u2013 the name of the host on which to modify omnirc or get omnirc value from\r\nvalue     \u2013 the value of environment variable to be added or modified in omnirc file.\r\n<\/pre>\n<\/blockquote>\n<p>If a value is omitted, the variable will be removed from omnirc file. If file omnirc does no exist, a new file will be generated on client. If a variable already exists, its value will be changed in-place, otherwise the new variable will be appended to omnirc file. The command can be used too for reading variables and values from clients.<\/p>\n<p>Example to be used to further automate distribution of omnirc parameter (read non existing variable, set variable, read existing variable):<\/p>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px\">\r\nC:\\Program Files\\OmniBack\\bin>util_cmd.exe -getomnirc w2012r2dp.localdomain OB2IPCKEEPALIVE\r\n*RETVAL*0\r\n\r\nC:\\Program Files\\OmniBack\\bin>util_cmd.exe -setomnirc w2012r2dp.localdomain OB2IPCKEEPALIVE 1\r\n*RETVAL*0\r\n\r\nC:\\Program Files\\OmniBack\\bin>util_cmd.exe -getomnirc w2012r2dp.localdomain OB2IPCKEEPALIVE\r\n1\r\n*RETVAL*0\r\n<\/pre>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>You know Data Protector? So you know that the modification of parameter for Data Protector is done in file global and in file omnirc. The file global is maintained on the Cell Server directly, but the file omnirc (Linux\/HP-UX: \/opt\/omni, Windows 2008 C:\\programdata\\omniback) has to be maintained on each client individually. The Data Protector admin [&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":[],"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-w3","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":1987,"position":0},"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":1987,"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":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":1987,"position":2},"title":"Advisory c03753986","date":"25. May 2013","format":false,"excerpt":"{:en}With document ID c03753986 on 2013\/05\/06 an advisory for HP Data Protector 6.11, 6.20, 6.21, 7.0 and 7.01 was released, describing a problem for restores of SAP data files and the file size is different from the SAP data file. When the omnirc parameter OB2SAPALIGN was used on Unix a\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1480,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/data-protector-8-00-cifs-share-backup\/","url_meta":{"origin":1987,"position":3},"title":"Data Protector 8.00 and CIFS Share Backup","date":"5. July 2013","format":false,"excerpt":"{:en}When using Data Protector 8.00 to backup a CIFS share (Network Share Backup), no matter if it is a Windows share or NetApp Filer, it could happen that the job does not backup any data from the share. In more detail, when selecting to backup all folders for the share\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1155,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":1987,"position":4},"title":"Hanging Sessions with DP 7.01","date":"23. January 2014","format":false,"excerpt":"{:en}It has been told to me and I've seen it in some environments... with DP 7.01 it can occur that a sessions hang till forever or the backup is aborted after 7200 second. The message displayed shows IPC errors (i.e error below) as no more data from Disk Agent or\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":935,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/05\/dp-7-0-omnirc-variable\/","url_meta":{"origin":1987,"position":5},"title":"DP 7.0 &#8211; omnirc &#8211; connection abort","date":"4. May 2012","format":false,"excerpt":"{:de}Mit Data Protector 7.0 kann es beim Backup zu untenstehender Fehlermeldung kommen. Der Fehler wurde in einem Case best\u00e4tigt. Zur L\u00f6sung kann in der omnirc die Variable OB2INETTIMEOUT=10 auf den betroffenen Clients aktiviert werden. Danke an Dennis Lorentsen der die Information bereitgestellt hat. Error: [Major] From: BSM@cellmanager.local \u201ctest_1\u2033 Time: 01-05-2012\u2026","rel":"","context":"In &quot;Bugs&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1987"}],"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=1987"}],"version-history":[{"count":8,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1987\/revisions"}],"predecessor-version":[{"id":3075,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1987\/revisions\/3075"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}