{"id":3952,"date":"2018-04-20T12:00:57","date_gmt":"2018-04-20T11:00:57","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=3952"},"modified":"2018-06-16T10:10:52","modified_gmt":"2018-06-16T09:10:52","slug":"effectively-manage-omnirc-options","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2018\/04\/effectively-manage-omnirc-options\/","title":{"rendered":"Effectively manage omnirc options"},"content":{"rendered":"

Data Protector is highly customizable product with a wide range of configuration options. While the any\u00a0global<\/strong> options applies to the whole Cell, the omnirc<\/strong> 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 of individual clients this can become a management challenge to make sure the right omnirc options are present on the right the client system.<\/p>\n

Over the years several ways to deal with this has been found, e.g. the script omnircsync.pl<\/em>\u00a0(available in the download section<\/a>) using the\u00a0util_cmd -setomnirc <\/em>push functionality. This functionality is adopted with the release of Data Protector A.10.03\u00a0<\/strong>into the product. We want to share some pretty handy use cases and examples of the new\u00a0omnicc -update_omnirc<\/em> command.<\/p>\n

It allows to push one omnirc option (key\/value pair) at a time and you can select a specific operating system type, client systems with a specific agent installed or a set of hosts in a comma separated list or from a input file.<\/p>\n

omnicc -update_omnirc omnircName -value omnircValue\r\n        [{ {-module moduleName1 [,moduleName2,..]} |\r\n        {-client_os osName1 [,osName2,..]} |\r\n        {inputFile | {-hosts hostName[,hostName2,..]}} }]<\/em>\r\n\r\nOptions:<\/strong>\r\nmoduleName = da, ma, cc, mssql70, oracle8, vepa, (as found in cell_info file)\r\nosName\u00a0= gpl, microsoft, sun, ... (as found in cell_info file)<\/pre>\n
<\/p>\n
Disable additional tree walk on all Windows clients<\/h3>\n
C:\\>omnicc -update_omnirc OB2NOTREEWALK -value 1 -client_os microsoft<\/em>\r\nwin01.syncer.de Success\r\nwin02.syncer.de Success\r\n[...]\r\nwin91.syncer.de Success\r\nwin92.syncer.de Success<\/pre>\n
Suppress the cross-mount point backup warnings on Linux clients<\/h3>\n
C:\\>omnicc -update_omnirc OB2NOREMOTEWARNINGS -value 1 -client_os gpl<\/em>\r\nlnx01.syncer.de Success\r\nlnx02.syncer.de Success\r\n[...]\r\nlnx19.syncer.de Success\r\nlnx20.syncer.de Success<\/pre>\n
Change the DNS timeout on all clients in the Cell<\/h3>\n
C:\\>omnicc -update_omnirc OB2_DNSTIMEOUT -value 2<\/em>\r\nesx01.syncer.del Skip - no core components\r\nesx02.syncer.de Skip - no core components\r\n[...]\r\nwin91.syncer.de Success\r\nwin92.syncer.de Success<\/pre>\n
Optimize all clients with the Microsoft SQL Server agent for performance<\/h3>\n
C:\\>omnicc -update_omnirc OB2SQLBLOCKSIZE -value 65536 -module mssql70<\/em>\r\nwin13.syncer.de Success\r\n\r\nC:\\>omnicc -update_omnirc OB2SQLMAXTRANSFERSIZE -value 4194304 -module mssql70<\/em>\r\nwin13.syncer.de Success<\/pre>\n
Define settings to an individual client system<\/h3>\n
C:\\>omnicc -update_omnirc OB2FORCESCSI -value\u00a0WFM -hosts lnx10.syncer.de<\/em>\r\nlnx10.syncer.de Success\r\n\r\nC:\\>omnicc -update_omnirc OB2IMMEDFM -value 1 -hosts lnx10.syncer.de<\/em>\r\nlnx10.syncer.de Success<\/pre>\n","protected":false},"excerpt":{"rendered":"
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 of individual clients this can […]<\/p>\n","protected":false},"author":5,"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":true,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-11K","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":935,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/05\/dp-7-0-omnirc-variable\/","url_meta":{"origin":3952,"position":0},"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":1987,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/","url_meta":{"origin":3952,"position":1},"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":3072,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/05\/script-distribute-omnirc-file\/","url_meta":{"origin":3952,"position":2},"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 "HowTo"","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":4164,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/06\/optimize-mssql-backup-performance\/","url_meta":{"origin":3952,"position":3},"title":"Optimize MSSQL backup performance","date":"20. June 2018","format":false,"excerpt":"{:en}Optimizing performance has always been a hot topic. This post contains information on how to optimize your MSSQL backup performance with the Data Protector. As always, with this kind of advice, this MAY be helpful in most environments but is not a general solution for any environment. Please test any\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"https:\/\/i1.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/05\/2018-05-24_18h22_22-450x323.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":3952,"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":2237,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/fiveminutestorunyourdataprotectorinstallationserveronlinux\/","url_meta":{"origin":3952,"position":5},"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":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3952"}],"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\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=3952"}],"version-history":[{"count":33,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3952\/revisions"}],"predecessor-version":[{"id":4235,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3952\/revisions\/4235"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=3952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=3952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=3952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}