{"id":1517,"date":"2013-07-19T06:14:57","date_gmt":"2013-07-19T05:14:57","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1517"},"modified":"2015-12-09T18:50:06","modified_gmt":"2015-12-09T17:50:06","slug":"virtual-environment-backups-vmware-storeonce-aborting-randomly","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/virtual-environment-backups-vmware-storeonce-aborting-randomly\/","title":{"rendered":"Virtual Environment Backups (VMware) to StoreOnce aborting randomly"},"content":{"rendered":"<p>Bei der Sicherung virtueller Maschinen mit der Virtual Environment Integration (VE) auf ein Catalyst Gateway (StoreOnce) kann es unter Data Protector 7.01 (aktuelle Patches) zu einem Abbruch bei der Sicherung kommen. Die Fehlermeldung sieht so aus:<\/p>\n<pre>\r\n[Major] From: B&#83;&#x4d;&#x40;&#x73;e&#114;&#x76;&#x65;&#x72;.&#100;&#x65;&#x6d;&#x6f;.&#108;&#x6f;&#x63;&#x61;l \"VE_Backup_VMware\"  Time: 15\/07\/2013 10:03:03\r\n[61:3003]      Lost connection to BMA named \"StoreOnce_01_GW1 [GW 2296:4:26641437476]\"  \r\n        on host server.demo.local.\r\n        Ipc subsystem reports: \"IPC Read Error\r\n        System error: [10054] Connection reset by peer\r\n<\/pre>\n<p>Abhilfe schafft der omnirc Parameter <code>OB2D2D_BANDWIDTH_BUFF_SIZE=20<\/code> auf dem Media Agent. Der Parameter ist unter DP 7.01 auf den Standardwert 10 eingestellt, bei Verwendung von 20 f\u00fcr den Wert tritt das Problem nicht auf. Data Protector 8.00 ist hiervon nicht betroffen, da hier der Standardwert auf 20 eingestellt ist.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bei der Sicherung virtueller Maschinen mit der Virtual Environment Integration (VE) auf ein Catalyst Gateway (StoreOnce) kann es unter Data Protector 7.01 (aktuelle Patches) zu einem Abbruch bei der Sicherung kommen. Die Fehlermeldung sieht so aus: [Major] From: BSM&#64;ser&#118;&#101;&#114;&#46;&#x64;&#x65;&#x6d;&#x6f;&#x2e;&#x6c;&#x6f;&#x63;&#x61;l &#8222;VE_Backup_VMware&#8220; Time: 15\/07\/2013 10:03:03 [61:3003] Lost connection to BMA named &#8222;StoreOnce_01_GW1 [GW 2296:4:26641437476]&#8220; on host server.demo.local. [&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-ot","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1155,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":1517,"position":0},"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":1623,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/10\/dp-8-ve-integration-requested-operation-timed\/","url_meta":{"origin":1517,"position":1},"title":"DP 8.0 and VE integration &#8211; requested operation timed out","date":"14. Oktober 2013","format":false,"excerpt":"{:en}With Data Protector 8.0 and when a backup for virtual machines, using the \"Virtual Environment Integration\", is performed, a message might be displayed \"Requested operation timed out\". The message has been seen, when long-running snapshots are created by the Virtual Center server. The timeout occurs after 60 seconds. The root\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1328,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/04\/vmware-backup-nbd-san\/","url_meta":{"origin":1517,"position":2},"title":"VMware backup done over NBD instead of SAN","date":"11. April 2013","format":false,"excerpt":"{:en}Problem: The backup of some virtual machines is done using transport mode NBD instead of SAN, even if it is configured for the virtual machine or a vApp container. There might be other virtual machines on the same SAN disk, which are able to do the backup over SAN. The\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1365,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/ipc-invalid-packet-size\/","url_meta":{"origin":1517,"position":3},"title":"IPC Invalid Packet Size","date":"8. Mai 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":[]},{"id":1478,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/write-device-parameter-incorrect\/","url_meta":{"origin":1517,"position":4},"title":"Cannot write to device &#8211; the parameter is incorrect","date":"5. Juli 2013","format":false,"excerpt":"{:en}When using the wrong block size for the tape devices, you may get the error message Cannot write to device ([87] The Parameter is incorrect.) during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try\u2026","rel":"","context":"In &quot;HowTo&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":1517,"position":5},"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":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1517"}],"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=1517"}],"version-history":[{"count":6,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1517\/revisions"}],"predecessor-version":[{"id":2629,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1517\/revisions\/2629"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}