{"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\/de\/2016\/05\/script-distribute-omnirc-file\/","title":{"rendered":"Script to distribute omnirc file"},"content":{"rendered":"

Seit Data Protector 8.11 ist es m\u00f6glich die omnirc Variablen f\u00fcr die Data Protector Clients \u00fcber ein Befehl zu setzen oder zu \u00e4ndern. In einem fr\u00fcheren Artikel hatte ich bereits dar\u00fcber berichtet – siehe https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/<\/a>. Mit der omnirc Datei wird das Verhalten eines Clients gesteuert und ist auch aus Sicht der Performance einer Sicherung wichtig. In der Data Protector Standard Einstellung ist die Datei nicht vorhanden und muss \u00fcberlicherweise aus dem Template generiert werden. Damit dies nicht manuell f\u00fcr alle Clients oder mit dem im Artikel erl\u00e4uterten Befehl util_cmd<\/code> durchgef\u00fchrt werden muss, hat Sebastian K\u00f6hler (http:\/\/www.syncer.de<\/a>) daf\u00fcr ein Perl Skript zur Verf\u00fcgung gestellt. Danke Sebastian! Das Skript befindet sich am Ende des Artikels oder im Downloadbereich.<\/p>\n

Das Skript ist recht einfach zu bedienen – siehe Screenshot.
\n\"omnircsync\"\/\n<\/p>\n

\nEinstellungen k\u00f6nnen entweder auf alle Clients, einzelne Betriebssysteme oder Data Protector Module verteilt werden. Das Skript arbeitet interaktiv oder nicht interaktiv und ben\u00f6tigt als Template eine (ASCII formatierte) Datei mit den Werten die gesetzt werden sollen.<\/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 368 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":"
Seit Data Protector 8.11 ist es m\u00f6glich die omnirc Variablen f\u00fcr die Data Protector Clients \u00fcber ein Befehl zu setzen oder zu \u00e4ndern. In einem fr\u00fcheren Artikel hatte ich bereits dar\u00fcber berichtet – siehe https:\/\/www.data-protector.org\/wordpress\/2014\/05\/distribute-omnirc-file\/. Mit der omnirc Datei wird das Verhalten eines Clients gesteuert und ist auch aus Sicht der Performance einer Sicherung wichtig. […]<\/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":"de","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\/de\/2014\/05\/distribute-omnirc-file\/","url_meta":{"origin":3072,"position":0},"title":"Distribute omnirc File","date":"23. Mai 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":694,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":3072,"position":1},"title":"Data Protector Migration Unix to other OS","date":"29. Juli 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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1480,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/data-protector-8-00-cifs-share-backup\/","url_meta":{"origin":3072,"position":2},"title":"Data Protector 8.00 and CIFS Share Backup","date":"5. Juli 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 "Common"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3162,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/07\/script-execution-dp-9-07\/","url_meta":{"origin":3072,"position":3},"title":"Script Execution with DP 9.07 – increased security","date":"15. Juli 2016","format":false,"excerpt":"{:en} With the introduction of HPE Data Protector 9.07 further action has been taken in the direction of security. Performing pre- and post-exec scripts might no longer permitted after the upgrade and instead an error is displayed. [Major] From: BSM@w2012rdp.localdomain \"dbbackup\" Time: 05.07.2016 11:35:01 Session post-exec script C:\\test\\startme.cmd failed. Exit\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1393,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":3072,"position":4},"title":"Advisory c03753986","date":"25. Mai 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":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":3072,"position":5},"title":"Installation order of Patches","date":"3. Juni 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 "History"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/3072"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/comments?post=3072"}],"version-history":[{"count":9,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/3072\/revisions"}],"predecessor-version":[{"id":3988,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/3072\/revisions\/3988"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media\/3074"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=3072"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=3072"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=3072"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}