{"id":183,"date":"2010-09-21T10:56:15","date_gmt":"2010-09-21T08:56:15","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=183"},"modified":"2015-12-10T11:17:11","modified_gmt":"2015-12-10T10:17:11","slug":"systemstate-sicherung-windows-error-8152","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/09\/systemstate-sicherung-windows-error-8152\/","title":{"rendered":"SystemState Backup Windows &#8211; Error [81:52]"},"content":{"rendered":"<p>Bei Windows Sicherung und installiertem Automated Disaster Recovery Modul kann es manchmal passieren das man bei\u00a0einer Sicherung des Systemstates von Windows (Configurationssicherung) diese Meldung erh\u00e4lt.<\/p>\n<p><code>[Critical] From: VBDA@CLIENT \"CONFIGURATION:\" Time: 21.09.2010 09:20:32<br \/>\n[81:52] \/CONFIGURATION<br \/>\nNot a valid mount point =&gt; aborting<\/code><\/p>\n<p>Die Erkl\u00e4rung wenn man auf den Link dr\u00fcckt ist dabei leider nicht hilfreich. Im debug.log stehen keine verwertbaren Informationen und ein autodr.log wurde nicht erstellt, da die Sicherung vorher abbricht. In der Regel hilft hier ein Reboot des Servers, ist aber nicht immer notwendig. In meinem Fall hatte es geholfen den zu sichernden Server mal genauer anzuschauen und ein Blick in <code>&lt;omnihome&gt;\\tmp\\config<\/code>\u00a0 zeigte das hier noch Reste der Configurationssicherung aus einem fr\u00fcheren Backupjob lagen (vermutlich eine abgebrochene Sicherung). Ich hatte einfach alles in <code>&lt;omnihome&gt;\\tmp\\config<\/code> gel\u00f6scht und dann funktionierte auch wieder die Sicherung des Systemstates von diesem Windows Server.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bei Windows Sicherung und installiertem Automated Disaster Recovery Modul kann es manchmal passieren das man bei\u00a0einer Sicherung des Systemstates von Windows (Configurationssicherung) diese Meldung erh\u00e4lt. [Critical] From: VBDA@CLIENT &#8222;CONFIGURATION:&#8220; Time: 21.09.2010 09:20:32 [81:52] \/CONFIGURATION Not a valid mount point =&gt; aborting Die Erkl\u00e4rung wenn man auf den Link dr\u00fcckt ist dabei leider nicht hilfreich. Im [&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":[82,84,83],"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-2X","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1150,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/09\/advisory-c03456297\/","url_meta":{"origin":183,"position":0},"title":"Advisory c03456297","date":"16. September 2012","format":false,"excerpt":"{:de}Unter der Dokument ID c03456297 ist am 14.08.2012 bei HP zu Data Protector 6.11, Data Protector 6.2 und Data Protector 7.0 ein Advisory erschienen, welches ein Problem beim Sichern von SharePoint Servern mit der Integration beschreibt. Folgende Fehlermeldung kann angezeigt werden, im Advisory werden die notwendigen Schritte zur Behebung erl\u00e4utert:\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":935,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2012\/05\/dp-7-0-omnirc-variable\/","url_meta":{"origin":183,"position":1},"title":"DP 7.0 &#8211; omnirc &#8211; connection abort","date":"4. Mai 2012","format":false,"excerpt":"{:de}Mit Data Protector 7.0 kann es beim Backup zu untenstehender Fehlermeldung kommen. Der Fehler wurde in einem Case best\u00e4tigt. Zur L\u00f6sung kann in der omnirc die Variable OB2INETTIMEOUT=10 auf den betroffenen Clients aktiviert werden. Danke an Dennis Lorentsen der die Information bereitgestellt hat. Error: [Major] From: BSM@cellmanager.local \u201ctest_1\u2033 Time: 01-05-2012\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\/de\/2014\/01\/hanging-sessions-dp-7-01\/","url_meta":{"origin":183,"position":2},"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":1480,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/data-protector-8-00-cifs-share-backup\/","url_meta":{"origin":183,"position":3},"title":"Data Protector 8.00 and CIFS Share Backup","date":"5. Juli 2013","format":false,"excerpt":"{:en}When using Data Protector 8.00 to backup a CIFS share (Network Share Backup), no matter if it is a Windows share or NetApp Filer, it could happen that the job does not backup any data from the share. In more detail, when selecting to backup all folders for the share\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1964,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/04\/advisory-ms-windows-2012-deduplication-hp-data-protector-data-loss\/","url_meta":{"origin":183,"position":4},"title":"Advisory: MS Windows 2012 Deduplication and HP Data Protector &#8211; Possible Data Loss","date":"23. April 2014","format":false,"excerpt":"{:en}Since MS Windows 2012 is supported with Data Protector, the disk agent is able to backup and restore files from deduplicated volumes. However, when the deduplicated volume is mounted into NTFS folder, the disk agent cannot recognize the deduplicated volume and hence, cannot backup the Chunk Store. No error messages\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":500,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/05\/cannot-connect-to-the-scm-omniinetpasswd\/","url_meta":{"origin":183,"position":5},"title":"Cannot connect to the SCM &#8211; omniinetpasswd","date":"9. Mai 2011","format":false,"excerpt":"{:en}During a push installation of the Data Protector Client to a Windows 2008 box, you may receive following error. In the internet or in the documentation of Data Protector you'll find the needed steps to address this error message. To be complete... it is also posted here. Cannot connect to\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\/183"}],"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=183"}],"version-history":[{"count":13,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/183\/revisions"}],"predecessor-version":[{"id":2449,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/183\/revisions\/2449"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}