{"id":1940,"date":"2014-04-04T05:00:05","date_gmt":"2014-04-04T04:00:05","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1940"},"modified":"2015-12-09T18:27:08","modified_gmt":"2015-12-09T17:27:08","slug":"advisory-dp-8-11-patch-bundle-ve-integration","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/04\/advisory-dp-8-11-patch-bundle-ve-integration\/","title":{"rendered":"Solution: DP 8.11 Patch Bundle and VE Integration"},"content":{"rendered":"<p>Beim Einsatz der Data Protector VMware Integration und nach Installation des Patch Bundle 8.11 kann es vorkommen, dass die Sicherung der virtuellen Maschinen nicht funktioniert. Das Problem tritt nur auf deutschen vCenter Servern auf, da der Root Path f\u00fcr das Datacenter als &#8222;Datencenter&#8220; zur\u00fcckgemeldet wird. Die L\u00f6sung ist die Installation eines Hotfixes. Wenn die Session Messages, wie unten dargestellt, auftreten, kann in diesem Fall ein Support Case ge\u00f6ffnet werden und der Hotfix QCCR2A52103 angefragt werden. Ein Workaround ist die das \u00c4ndern der group-d1 Eigenschaft. Dazu ist der &#8222;Managed Object Browser&#8220; auf dem vCenter Server (https:\/\/localhost\/mob) zu \u00f6ffnen, &#8222;content&#8220; auszuw\u00e4hlen und die Eigenschaft der group-d1 von &#8222;rootFolder ManagedObjectReference:Folder group-d1 <b>(Datencenter)<\/b>&#8220; auf &#8222;rootFolder ManagedObjectReference:Folder group-d1 <b>(Datacenters)<\/b>&#8220; zu \u00e4ndern.<\/p>\n<blockquote style=\"font: 12px Courier; background-color: #ffffff; border: 1px solid #ccc; border-radius: 6px; box-shadow: 1px 1px 1px #ccc;\">\n<pre style=\"border: 0px\">\r\n[Normal] From: &#x42;&#x53;M&#64;&#x73;&#x65;&#114;ve&#x72;&#x2e;do&#x61;&#x6d;&#105;n \"VEPA_TEST\"  Time: 03.04.2014 17:05:29\r\n\tBackup session 2014\/04\/03-40 started.\r\n\r\n[Normal] From: &#x42;S&#x4d;&#x40;s&#x65;&#114;v&#x65;&#114;.&#x64;&#111;a&#x6d;&#105;n \"VEPA_TEST\"  Time: 03.04.2014 17:05:29\r\n\tOB2BAR application on \"server.doamin\" successfully started.\r\n\r\n[Normal] From: &#86;&#x45;&#80;&#x41;&#76;&#x49;&#66;&#x5f;&#86;&#x4d;W&#x41;R&#x45;&#64;&#x73;e&#x72;v&#x65;r&#x2e;d&#x6f;a&#x6d;i&#x6e; \"\/Datacenter\"  Time: 03.04.2014 17:05:30\r\n\tResolving objects for backup on vCenter 'server1.doamin' ... \r\n\r\n[Major] From: &#x56;&#x45;&#80;AL&#x49;&#x42;&#95;VM&#x57;&#x41;&#82;E&#64;&#x73;&#x65;&#x72;ver&#x2e;&#x64;&#111;am&#x69;&#x6e; \"\/Datacenter\"  Time: 03.04.2014 17:05:37\r\n\tBackup failed.\r\n\r\n[Normal] From: BSM&#64;ser&#118;&#101;&#114;&#46;&#x64;&#x6f;&#x61;&#x6d;&#x69;&#x6e; \"VEPA_TEST\"  Time: 03.04.2014 17:06:14\r\n\tOB2BAR application on \"server.doamin\" disconnected.\r\n<\/pre>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Beim Einsatz der Data Protector VMware Integration und nach Installation des Patch Bundle 8.11 kann es vorkommen, dass die Sicherung der virtuellen Maschinen nicht funktioniert. Das Problem tritt nur auf deutschen vCenter Servern auf, da der Root Path f\u00fcr das Datacenter als &#8222;Datencenter&#8220; zur\u00fcckgemeldet wird. Die L\u00f6sung ist die Installation eines Hotfixes. Wenn die Session [&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-vi","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":4315,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2018\/09\/data-protector-10-updated-release-a-10-10-build-xxx\/","url_meta":{"origin":1940,"position":0},"title":"Data Protector 10 \u2013 Updated Release A.10.10 (Build 134)","date":"18. September 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.10 (Build 134)\u00a0has been released on September 17, 2018. The new version is another full install to simplify the upgrade and installation process.This will be the default for all future Data Protector versions. Data Protector 10.10 does not require any previous version to install the latest version of Data\u2026","rel":"","context":"In &quot;DP A.10.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3581,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2017\/03\/data-protector-9-patch-bundle-9-09-build-114\/","url_meta":{"origin":1940,"position":1},"title":"Data Protector 9 \u2013 Patch Bundle 9.09 (Build 114)","date":"30. M\u00e4rz 2017","format":false,"excerpt":"{:en}The Patch Bundle A.09.09 (Build 114) for Data Protector 9 has been released on March 30, 2017. The cumulative patch can be installed on top of A.09.00 or any later Patch Bundle or General Release patch. It is recommended to install it on all Installation Servers (IS) and the Cell\u2026","rel":"","context":"In &quot;DP A.09.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"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":1940,"position":2},"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":[]},{"id":2372,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/08\/tested-poweronrun-live-migrate-3par-snapshots-smartcache\/","url_meta":{"origin":1940,"position":3},"title":"TESTED: PowerOn&#038;Run and Live Migrate from 3PAR Snapshots or SmartCache","date":"27. August 2015","format":false,"excerpt":"{:en} With Data Protector 9.04 the new features PowerOn & Run and Live Migrate from 3PAR snapshots or SmartCache were introduced. This feature allows to power on and test virtual machines (VMware), backed up using the VE integration. Recently I had the opportunity to implement this feature in a proof\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2262,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/01\/data-protector-9-02-features-explained\/","url_meta":{"origin":1940,"position":4},"title":"Data Protector 9.02 features explained","date":"27. Januar 2015","format":false,"excerpt":"{:en} In December HP released the new Data Protector version 9.02. With this release additional features were implemented. Some of the new features are explained in more detail below. New Data Protector features: Pausing and Resuming Backup Jobs Reporting for Capacity Based Licensing VMware GRE for 3PAR Snapshots StoreOnce CoFC\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":1940,"position":5},"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":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1940"}],"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=1940"}],"version-history":[{"count":7,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1940\/revisions"}],"predecessor-version":[{"id":2585,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1940\/revisions\/2585"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}