{"id":3072,"date":"2016-05-18T06:05:11","date_gmt":"2016-05-18T05:05:11","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=3072"},"modified":"2016-06-10T16:24:33","modified_gmt":"2016-06-10T15:24:33","slug":"script-distribute-omnirc-file","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2016\/05\/script-distribute-omnirc-file\/","title":{"rendered":"Script to distribute omnirc file"},"content":{"rendered":"

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\/<\/a>. Using omnirc settings you can control the client behavior and is important from performance point of view too. With the Data Protector default settings the omnirc file is not present and usually has to be created from the template file. To prevent manual work, either by copying the file or using the command util_cmd<\/code>, Sebastian K\u00f6hler (http:\/\/www.syncer.de<\/a>) wrote a Perl script automating all the stuff. Kudos to Sebastian! The script can be found at the end of the article or in download section.<\/p>\n

The script is very handy and easy to use – see screenshot.
\n\"omnircsync\"\/\n<\/p>\n

\nThe settings can be distributed to all clients, clients with selected operating system, or clients with selected Data Protector modules. The script either works interactive or non-interactive and requires an ASCII formatted template file with the parameter you want to apply.<\/p>\n

\n
\r\nc:\\>perl omnircsync.pl omnirc -os microsoft\r\n-------------------------------------------------------------------------------\r\nClients that will receive parameters from omnirc template:\r\n-------------------------------------------------------------------------------\r\n[X] sqldemo\r\n[ ] ubuntuvm.localdomain\r\n[X] w2012r2dp.localdomain\r\n-------------------------------------------------------------------------------\r\n\r\n-------------------------------------------------------------------------------\r\nParameter found in omnirc template:\r\n-------------------------------------------------------------------------------\r\nOB2DEVMUTEXTIMEOUT=12000\r\nOB2FILELIBDISKFULL=1\r\nOB2FWPASSTHRU=1\r\nOB2INETTIMEOUT=10\r\n... \r\nOB2NOREMOTEWARNINGS=1\r\nOB2NOTREEWALK=1\r\nOB2_SSH_ENABLED=1\r\n-------------------------------------------------------------------------------\r\n\r\nINTERACTIVE mode: enabled\r\n\r\nPlease confirm push operation to 2 clients? (Y\/N) y\r\n\r\n-------------------------------------------------------------------------------\r\nSynchronization of omnirc started:\r\n-------------------------------------------------------------------------------\r\n=> sqldemo: [DONE]\r\n=> w2012r2dp.localdomain: [DONE]\r\n-------------------------------------------------------------------------------\r\n<\/pre>\n<\/blockquote>\n
Download:<\/b>
\nomnircsync.zip
\n
\n\n\n
\n    
\n        
\"Icon\"<\/div>\n        
omnircsync.pl 367 downloads<\/span> 4.33 KB<\/span><\/strong>\n            
omnircsync.pl<\/a><\/strong><\/div>\n        <\/div>\n    <\/div>\n<\/div>\n
<\/div>\n<\/div><\/p>\n","protected":false},"excerpt":{"rendered":"
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 too. With the Data Protector default […]<\/p>\n","protected":false},"author":1,"featured_media":3074,"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":"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/omnircsync.png","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-Ny","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1987,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/","url_meta":{"origin":3072,"position":0},"title":"Distribute omnirc File","date":"23. May 2014","format":false,"excerpt":"{:en} 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\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3952,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/04\/effectively-manage-omnirc-options\/","url_meta":{"origin":3072,"position":1},"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 "HowTo"","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":3072,"position":2},"title":"DP 7.0 – omnirc – 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 "Bugs"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2237,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/fiveminutestorunyourdataprotectorinstallationserveronlinux\/","url_meta":{"origin":3072,"position":3},"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 "HowTo"","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":3072,"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 "Advisory"","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":3072,"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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3072"}],"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=3072"}],"version-history":[{"count":9,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3072\/revisions"}],"predecessor-version":[{"id":3988,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3072\/revisions\/3988"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media\/3074"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=3072"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=3072"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=3072"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}