{"id":1169,"date":"2012-10-01T09:26:14","date_gmt":"2012-10-01T07:26:14","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1169"},"modified":"2015-12-09T20:42:10","modified_gmt":"2015-12-09T19:42:10","slug":"dp-7-01-remote-installation-linux-working","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2012\/10\/dp-7-01-remote-installation-linux-working\/","title":{"rendered":"DP 7.01 remote installation Linux not working"},"content":{"rendered":"<p>With Data Protector 7.01 there might be a problem when doing a remote installation of a Linux Client with Kernel 3 (i.e. SLES 11 SP2). In the GUI you might receive an error that the client is not supportet. This is a known problem and was fixed in previous versions (was announced for DP 7.01 too), however, with current DP 7.01 the problem still exist. Following solutions apply to the problem:<\/p>\n<ul>\n<li>Open a case and request hotfix QCCR2A36254_TM2 and QCCR2A38378. The first fix includes fixed bmsetup and .util file, the 2nd fix fixes the display problem in the GUI (unknown client).<\/li>\n<li>Local installation of core.rpm and da.rpm and import of the client in GUI, the display problem will not be fixed with this workaround.<\/li>\n<li>Wait for further release of patches: patch DPWIN_00614, DPWIN_006?? and DPWIN_006?? (Core, CS, CC) and PHSS_43??? \/ DPLNX_002?? (Core).<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>With Data Protector 7.01 there might be a problem when doing a remote installation of a Linux Client with Kernel 3 (i.e. SLES 11 SP2). In the GUI you might receive an error that the client is not supportet. This is a known problem and was fixed in previous versions (was announced for DP 7.01 [&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":[1],"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-iR","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1419,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/nss-volumes-linux-oes\/","url_meta":{"origin":1169,"position":0},"title":"NSS Volumes on Linux OES","date":"4. June 2013","format":false,"excerpt":"{:en}When you need to backup NSS volumes on a Linux OES server with Data Protector 7.01 - current patches, it might be the case that the NSS volumes are not listed within GUI and you might receive the following error: 12:1304 The mountpoint\/file-system cannot be backed up. Probally you might\u2026","rel":"","context":"In &quot;Bugs&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1155,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":1169,"position":1},"title":"Hanging Sessions with DP 7.01","date":"23. January 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":1517,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/virtual-environment-backups-vmware-storeonce-aborting-randomly\/","url_meta":{"origin":1169,"position":2},"title":"Virtual Environment Backups (VMware) to StoreOnce aborting randomly","date":"19. July 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":1077,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/10\/current-patches-dp-7-0-7-01-7-03\/","url_meta":{"origin":1169,"position":3},"title":"Current Patches DP 7.0 \/ 7.01 \/ 7.03","date":"24. October 2013","format":false,"excerpt":"{:en}Update: On 2013\/10\/24 HP delivered the patch bundle 7.03 for Linux, HP-UX and Windows. The update will fix many problems and enhances support for integrations and new features. Because of the changes it is recommended to read the full description of the bundle. Old Messages have been removed. If you\u2026","rel":"","context":"In &quot;DP A.07.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1333,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/04\/changed-syntax-omnib2dinfo\/","url_meta":{"origin":1169,"position":4},"title":"Changed syntax for omnib2dinfo","date":"15. April 2013","format":false,"excerpt":"{:en}omnib2dinfo: With the lastest released patches for DP 7.01 from 2013\/04\/09 there was a change in the syntax for the command omib2dinfo. In previous versions it was required to provide parameters like device type and host name to retrieve information from the B2D device, no matter if a software store\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1320,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/03\/advisory-c03705726\/","url_meta":{"origin":1169,"position":5},"title":"Advisory c03705726","date":"26. March 2013","format":false,"excerpt":"{:en}With document ID c03705726 on 2013\/03\/20 an advisory for HP Data Protector and 7.0 (7.01) was released, describing a problem when a backup was taken to a backup to disk device and in restore context of DP GUI the file size is displayed as zero. As a workaround the list\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\/wp-json\/wp\/v2\/posts\/1169"}],"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=1169"}],"version-history":[{"count":6,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1169\/revisions"}],"predecessor-version":[{"id":2682,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1169\/revisions\/2682"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1169"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1169"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1169"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}