{"id":1365,"date":"2013-05-08T13:42:11","date_gmt":"2013-05-08T12:42:11","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1365"},"modified":"2015-12-09T19:01:31","modified_gmt":"2015-12-09T18:01:31","slug":"ipc-invalid-packet-size","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/ipc-invalid-packet-size\/","title":{"rendered":"IPC Invalid Packet Size"},"content":{"rendered":"<p>Nach einem Upgrade auf Data Protector 7.01 kann es selten zu folgender Fehlermeldung beim Zugriff auf Changer oder Bandlaufwerke kommen: <code>IPC Invalid Packet Size<\/code>. Grund hierf\u00fcr kann eine langsame Namensaufl\u00f6sung auf dem Media Agent sein, so dass der INET Timout eintritt bevor eine Antwort an den entsprechenden Prozess gesendet werden kann. Die bereits bekannte omnirc Variable OB2INETTIMEOUT kann in diesem Fall vom Wert 10 auf einen h\u00f6heren Wert (z.B. 30) gesetzt werden. Der neue Wert &#8211; <code>OB2INETTIMEOUT=30<\/code> muss auf dem betroffenen Media Agenten in der omnirc gespeichert werden.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nach einem Upgrade auf Data Protector 7.01 kann es selten zu folgender Fehlermeldung beim Zugriff auf Changer oder Bandlaufwerke kommen: IPC Invalid Packet Size. Grund hierf\u00fcr kann eine langsame Namensaufl\u00f6sung auf dem Media Agent sein, so dass der INET Timout eintritt bevor eine Antwort an den entsprechenden Prozess gesendet werden kann. Die bereits bekannte omnirc [&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":"de","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-m1","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1517,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/virtual-environment-backups-vmware-storeonce-aborting-randomly\/","url_meta":{"origin":1365,"position":0},"title":"Virtual Environment Backups (VMware) to StoreOnce aborting randomly","date":"19. Juli 2013","format":false,"excerpt":"{:en}When backing up virtual machines using the Virtual Environment Integration (VE) to a Catalyst Gateway (StoreOnce), with Data Protector 7.01 (current patches) the VEPA backups might aborting randomly. The error message displayed: [Major] From: BSM@server.demo.local \"VE_Backup_VMware\" Time: 15\/07\/2013 10:03:03 [61:3003] Lost connection to BMA named \"StoreOnce_01_GW1 [GW 2296:4:26641437476]\" on host\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1155,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":1365,"position":1},"title":"Hanging Sessions with DP 7.01","date":"23. Januar 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\/de\/2012\/05\/dp-7-0-omnirc-variable\/","url_meta":{"origin":1365,"position":2},"title":"DP 7.0 &#8211; omnirc &#8211; connection abort","date":"4. Mai 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\/de\/2013\/05\/advisory-c03753986\/","url_meta":{"origin":1365,"position":3},"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 &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3879,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/03\/data-protector-10-updated-release-a-10-03-build-181\/","url_meta":{"origin":1365,"position":4},"title":"Data Protector 10 \u2013 Updated Release A.10.03 (Build 181)","date":"30. M\u00e4rz 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.03 (Build 181)\u00a0has been released on March 30, 2018. While you might expect a Patch Bundle, Micro Focus decided to simplify the upgrade and installation by delivering a full build. Data Protector 10.03 does not require any previous version to install the latest version of Data Protector in a\u2026","rel":"","context":"In &quot;DP A.10.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1987,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/05\/distribute-omnirc-file\/","url_meta":{"origin":1365,"position":5},"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 &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1365"}],"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=1365"}],"version-history":[{"count":5,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1365\/revisions"}],"predecessor-version":[{"id":2656,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1365\/revisions\/2656"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}