{"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\/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>After updating to vCenter 5.1 update 2 and with Data Protector 7.03 or 8.1X a blank page might be displayed when using VMware GRE. The reason might be a change in Tomcat of vCenter. When looking into the log files (i.e. C:\\ProgramData\\VMware\\VMware VirtualCenter\\Logs\\localhost.YYYY-MM-DD.log) the error <code>VMwareGRE: runCGI (stderr):Can't open perl script \"C:\\Program\": No such file or directory<\/code> might be displayed. As a workaround the config file <code>web.xml<\/code> of the VMware GRE plugin can be modified. When using a standard installation the file is located in <code>C:\\Program Files\\VMware\\Infrastructure\\tomcat\\webapps\\VMwareGRE\\WEB-INF\\<\/code>. The workaround will change how the parameters are handled.<\/p>\n<p>Change the 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;&#8221;C:\\Program Files\\OmniBack\\bin\\perl.exe&#8221; -I &#8220;C:\\Program Files\\OmniBack\\lib\\perl&#8221;<br \/>\n&lt;\/init&gt;\n<\/p><\/blockquote>\n<p>Changed 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>After updating to vCenter 5.1 update 2 and with Data Protector 7.03 or 8.1X a blank page might be displayed when using VMware GRE. The reason might be a change in Tomcat of vCenter. When looking into the log files (i.e. C:\\ProgramData\\VMware\\VMware VirtualCenter\\Logs\\localhost.YYYY-MM-DD.log) the error VMwareGRE: runCGI (stderr):Can&#8217;t open perl script &#8220;C:\\Program&#8221;: No such file [&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":"en","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":1710,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/01\/data-protector-8-10-whats-new\/","url_meta":{"origin":1884,"position":0},"title":"Data Protector 8.10 available &#8211; whats new?","date":"7. January 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":1866,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/03\/workaround-eadr-windows-2003-32-bit-data-protector-7-03\/","url_meta":{"origin":1884,"position":1},"title":"Workaround: EADR Windows 2003 32 Bit &#8211; Data Protector 7.03","date":"4. March 2014","format":false,"excerpt":"{:en} When using Data Protector 7.03 and when doing Enhanced Automated Disaster Recovery for a Windows 2003 32bit client, the restore might not work after the Mini OS has been started. You might recognize the starting omnidr process, however the preocess will run into a loop and the EADR process\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2957,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/03\/data-protector-gre-vmware-6-vcenter-server-appliance\/","url_meta":{"origin":1884,"position":2},"title":"Data Protector GRE with VMware 6 and vCenter Server Appliance","date":"9. March 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":1940,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/04\/advisory-dp-8-11-patch-bundle-ve-integration\/","url_meta":{"origin":1884,"position":3},"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":1328,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/04\/vmware-backup-nbd-san\/","url_meta":{"origin":1884,"position":4},"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":903,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/06\/backup-exec-no-longer-for-the-enterprise\/","url_meta":{"origin":1884,"position":5},"title":"Backup Exec no longer for the Enterprise","date":"7. June 2012","format":false,"excerpt":"{:de}Kurz und Knapp: Symantec hat in einem Artikel f\u00fcr Backup Exec 2012 einige seiner Komponenten auf EOL - end of life - gesetzt und verliert aus meiner Sicht die F\u00e4higkeit im Enterprise Backup & Recovery L\u00f6sungen anzubieten. Der Einsatz im Mittelstand ist fragw\u00fcrdig, da auch in diesem Bereich Anwendungen wie\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1884"}],"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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=1884"}],"version-history":[{"count":10,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1884\/revisions"}],"predecessor-version":[{"id":2590,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1884\/revisions\/2590"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1884"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1884"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1884"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}