{"id":1884,"date":"2014-03-25T21:50:57","date_gmt":"2014-03-25T20:50:57","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1884"},"modified":"2015-12-09T18:31:41","modified_gmt":"2015-12-09T17:31:41","slug":"workaround-vmware-gre-dp-7-038-1x-vcenter-5-1-u2","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/workaround-vmware-gre-dp-7-038-1x-vcenter-5-1-u2\/","title":{"rendered":"Workaround: VMware GRE &#8211; DP 7.03\/8.1X &#8211; vCenter 5.1 U2"},"content":{"rendered":"<p>Nach dem Update auf vCenter 5.1 Update 2 und unter Data Protector 7.03 oder 8.1X kann es bei Verwendung von VMware GRE zur Anzeige einer leeren Seite kommen. Grund hierf\u00fcr k\u00f6nnen \u00c4nderungen im Tomcat vom vCenter sein. Das Plugin von Data Protector (GRE) zeigt dann eine leere Seite an. Bei Kontrolle der Logdateien (z.B. C:\\ProgramData\\VMware\\VMware VirtualCenter\\Logs\\localhost.YYYY-MM-DD.log) wird der Fehler <code>VMwareGRE: runCGI (stderr):Can't open perl script \"C:\\Program\": No such file or directory<\/code> protokolliert. Als Workaround kann die Konfigurationsdatei <code>web.xml<\/code> des VMware GRE Plugins angepasst werden. Bei einer Standardinstallation kann die Datei unter <code>C:\\Program Files\\VMware\\Infrastructure\\tomcat\\webapps\\VMwareGRE\\WEB-INF\\<\/code> gefunden werden. Der Workaround \u00e4ndert die Art der Parameter \u00dcbergabe.<\/p>\n<p>\u00c4nderung des Blocks:<\/p>\n<blockquote style=\"font: 12px Courier; background-color: #f9f9f9; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\"><p>\n&lt;init -param&gt;<br \/>\n&lt;param -name\/&gt;executable<br \/>\n&lt;param -value\/&gt;&#8220;C:\\Program Files\\OmniBack\\bin\\perl.exe&#8220; -I &#8222;C:\\Program Files\\OmniBack\\lib\\perl&#8220;<br \/>\n&lt;\/init&gt;\n<\/p><\/blockquote>\n<p>Ge\u00e4nderter Block:<\/p>\n<blockquote style=\"font: 12px Courier; background-color: #f9f9f9; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\"><p>\n&lt;init -param&gt;<br \/>\n&lt;param -name\/&gt;executable<br \/>\n&lt;param -value\/&gt;C:\\Program Files\\OmniBack\\bin\\perl.exe<br \/>\n&lt;\/init&gt;<br \/>\n&lt;init -param&gt;<br \/>\n&lt;param -name\/&gt;executable-arg-1<br \/>\n&lt;param -value\/&gt;-I<br \/>\n&lt;\/init&gt;<br \/>\n&lt;init -param&gt;<br \/>\n&lt;param -name\/&gt;executable-arg-2<br \/>\n&lt;param -value\/&gt;C:\\Program Files\\OmniBack\\lib\\perl<br \/>\n&lt;\/init&gt;\n<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Nach dem Update auf vCenter 5.1 Update 2 und unter Data Protector 7.03 oder 8.1X kann es bei Verwendung von VMware GRE zur Anzeige einer leeren Seite kommen. Grund hierf\u00fcr k\u00f6nnen \u00c4nderungen im Tomcat vom vCenter sein. Das Plugin von Data Protector (GRE) zeigt dann eine leere Seite an. Bei Kontrolle der Logdateien (z.B. C:\\ProgramData\\VMware\\VMware [&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":[24],"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-uo","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":2957,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/03\/data-protector-gre-vmware-6-vcenter-server-appliance\/","url_meta":{"origin":1884,"position":0},"title":"Data Protector GRE with VMware 6 and vCenter Server Appliance","date":"9. M\u00e4rz 2016","format":false,"excerpt":"{:en} A new great article from Jim regarding HPE Data Protector and Granular Recovery Extension for VMware 6. A really good howto, worth to read. http:\/\/community.hpe.com\/t5\/Technical-Support-Services\/DPTIPS-Getting-DP-GRE-to-work-with-VMware-6-and-vCenter-Server\/ba-p\/6838870#.Vt3XHnn2a70 {:} {:de} Ein neuer gro\u00dfartiger Artikel von Jim zu HPE Data Protector und Granular Recovery Extension f\u00fcr VMware 6. Eine sehr gute und lesenswerte\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1710,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/data-protector-8-10-whats-new\/","url_meta":{"origin":1884,"position":1},"title":"Data Protector 8.10 available &#8211; whats new?","date":"7. Januar 2014","format":false,"excerpt":"{:en}Data Protector 8.10 has been released. The new version delivers some new features, my favorites are the new advanced scheduler and the file-system backup, which can be resumed. For customers with a valid support contract, the new version can be downloaded here: http:\/\/support.openview.hp.com. With Data Protector 8.1 new licenses are\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1940,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/04\/advisory-dp-8-11-patch-bundle-ve-integration\/","url_meta":{"origin":1884,"position":2},"title":"Solution: DP 8.11 Patch Bundle and VE Integration","date":"4. April 2014","format":false,"excerpt":"{:en}When using the Data Protector VE integration to backup virtual machines and after the installation of patch bundle 8.11 it might happen, that the backup of the virtual machines is not working. The problem occurs on German localized vCenter Servers only, as the root path for the datacenter is reported\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2893,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/02\/data-protector-7-03-patches-build-108\/","url_meta":{"origin":1884,"position":3},"title":"Data Protector 7.03 Patches (Build 108)","date":"1. Februar 2016","format":false,"excerpt":"{:en}On 2016\/01\/29 HPE released new patches for Linux, Windows and HP-UX. As a requirement you need to have Patch Bundle 7.03 installed. It is strongly recommended to read the full description of each patch. If you own a valid support contract you can download the patch from https:\/\/softwaresupport.hp.com. For login\u2026","rel":"","context":"In &quot;DP A.07.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3097,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/06\/hpe-data-protector-7-0x-8-0x-eol\/","url_meta":{"origin":1884,"position":4},"title":"HPE Data Protector 7.0X and 8.0X &#8211; EOL","date":"3. Juni 2016","format":false,"excerpt":"{:en} The time has come, this month the support for Data Protector 7.0x and 8.0x Data Protector will end. Support for version 8.1x will end 30\/06\/2017. Of course, all customers with an active maintenance contract can upgrade to the current Data Protector version 9.0x. Data Protector 9.0x includes enhancements like:\u2026","rel":"","context":"In &quot;Data Protector Links&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/06\/eol.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":4128,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/05\/data-protector-10-patch-bundle-a-10-04-build-182\/","url_meta":{"origin":1884,"position":5},"title":"Data Protector 10 \u2013 Patch Bundle A.10.04 (Build 182)","date":"23. Mai 2018","format":false,"excerpt":"{:en}The Patch Bundle A.10.04 (Build 182) for Data Protector 10 has been released on May 22, 2018. Data Protector A.10.03 was released as a full install therefore the cumulative patch 10.04 can only be installed on top of A.10.03. A direct upgrade from A.10.00, A.10.01 or A.10.02 is not possible!\u2026","rel":"","context":"In &quot;DP A.10.00&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\/1884"}],"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=1884"}],"version-history":[{"count":10,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1884\/revisions"}],"predecessor-version":[{"id":2590,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1884\/revisions\/2590"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}