{"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":3952,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/04\/effectively-manage-omnirc-options\/","url_meta":{"origin":1987,"position":0},"title":"Effectively manage omnirc options","date":"20. April 2018","format":false,"excerpt":"{:en}Data Protector is highly customizable product with a wide range of configuration options. While the any\u00a0global options applies to the whole Cell, the omnirc configuration file allows the user to tweak a specific client or just a module on that client system. It you have to manage a large amount\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3072,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/05\/script-distribute-omnirc-file\/","url_meta":{"origin":1987,"position":1},"title":"Script to distribute omnirc file","date":"18. May 2016","format":false,"excerpt":"{:en} Since Data Protector 8.11 version it is possible to distribute omnirc parameter for the Data Protector clients using a command. In a former article I informed about - please refer to https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/. Using omnirc settings you can control the client behavior and is important from performance point of view\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/omnircsync.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":2237,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/fiveminutestorunyourdataprotectorinstallationserveronlinux\/","url_meta":{"origin":1987,"position":2},"title":"Five Minutes to run your Data Protector Installation Server on Linux","date":"19. January 2015","format":false,"excerpt":"{:en} 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).\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":3},"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":[]},{"id":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":1987,"position":4},"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":1365,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/ipc-invalid-packet-size\/","url_meta":{"origin":1987,"position":5},"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":[]}],"_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}]}}