{"id":1927,"date":"2014-04-01T11:10:15","date_gmt":"2014-04-01T10:10:15","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1927"},"modified":"2015-12-10T19:32:06","modified_gmt":"2015-12-10T18:32:06","slug":"reviewed-persistent-binding-windows-2012","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/04\/reviewed-persistent-binding-windows-2012\/","title":{"rendered":"Reviewed: Persistent Binding Windows 2012"},"content":{"rendered":"<p>In einem fr\u00fcheren Artikel (siehe <a href=\"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/persistent-binding-hp-lto-tape-drives-windows\/\">https:\/\/www.data-protector.org\/wordpress\/2013\/05\/persistent-binding-hp-lto-tape-drives-windows\/<\/a>) hatte ich zu &#8222;Tape Persistence&#8220; f\u00fcr Windows berichtet. Prinzipiell \u00e4ndert sich an der Vorgehensweise f\u00fcr Windows 2012 nichts und die Registry Keys bleiben gleich. Voraussetzung ist jedoch, dass auf den Fibre Channel HBA &#8222;Target Persistent Binding&#8220; aktiviert ist. F\u00fcr QLogic Adapter kann dies mit dem Tool &#8222;QConvergeConsole&#8220; (ehemals SANSurfer) konfiguriert werden. F\u00fcr Emulex Adapter (HBAAnywhere) ist die Konfiguration \u00e4hnlich vorzunehmen. Nach Aktivieren und Konfigurieren auf dem Adapter, das Hinzuf\u00fcgen der Registry Keys und einem abschlie\u00dfenden Reboot, stehen die Laufwerke und Changer wie gewohnt &#8222;persistent&#8220; zur Verf\u00fcgung. Kommentar: Alle Angaben getestet mit HP Libraries und Laufwerken.<\/p>\n<p>Beispiel:<\/p>\n<p><img src=\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2014\/04\/qlogic_persistence.png\" alt=\"qlogic\"\/><\/p>\n<p>Registry:<\/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\nWindows Registry Editor Version 5.00\r\n\r\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\hplto]\r\n\"AutoRun\"=dword:00000000\r\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Tape]\r\n\"Persistence\"=dword:00000001\r\n[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\MChgr]\r\n\"Persistence\"=dword:00000001\r\n<\/pre>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>In einem fr\u00fcheren Artikel (siehe https:\/\/www.data-protector.org\/wordpress\/2013\/05\/persistent-binding-hp-lto-tape-drives-windows\/) hatte ich zu &#8222;Tape Persistence&#8220; f\u00fcr Windows berichtet. Prinzipiell \u00e4ndert sich an der Vorgehensweise f\u00fcr Windows 2012 nichts und die Registry Keys bleiben gleich. Voraussetzung ist jedoch, dass auf den Fibre Channel HBA &#8222;Target Persistent Binding&#8220; aktiviert ist. F\u00fcr QLogic Adapter kann dies mit dem Tool &#8222;QConvergeConsole&#8220; (ehemals SANSurfer) [&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":[11],"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-v5","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1345,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/05\/persistent-binding-hp-lto-tape-drives-windows\/","url_meta":{"origin":1927,"position":0},"title":"Persistent Binding for HP LTO tape drives on Windows","date":"8. Mai 2013","format":false,"excerpt":"{:en}\"Tape Persistence\" means that the tape drives for a tape library use symbolic names. These names stay unique during server reboots, no matter in which order the operating system discovers the tape drives. Without the feature during reboots it could be possible that the SCSI addresses are changed. Normally the\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":100,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/12\/disable-device-polling\/","url_meta":{"origin":1927,"position":1},"title":"Disable Device Polling","date":"31. Dezember 2010","format":false,"excerpt":"{:de}In einem anderen Artikel \"What is device polling\" \u00a0hatte ich beschrieben was Device Polling ist und welche Auswirkungen das auf ein backup haben kann. Hier versuche ich nun aufzuzeigen wie man Device Polling verhindert. Bleibt zu erw\u00e4hnen das nachfolgende Hinweise f\u00fcr anst\u00e4ndige Hardware - HP - gelten. Wenn man gezwungen\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":549,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/d2d-and-data-protector\/","url_meta":{"origin":1927,"position":2},"title":"D2D and Data Protector","date":"11. Juli 2011","format":false,"excerpt":"{:en}For a customer it could be interesting to enhance the backup and recovery strategy and to do the backup (or parts of the backup) to disk first and to copy the data to tape later. The main advantage is the reduced time it will take to recover a single file,\u00a0as\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1478,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/write-device-parameter-incorrect\/","url_meta":{"origin":1927,"position":3},"title":"Cannot write to device &#8211; the parameter is incorrect","date":"5. Juli 2013","format":false,"excerpt":"{:en}When using the wrong block size for the tape devices, you may get the error message Cannot write to device ([87] The Parameter is incorrect.) during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1866,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/03\/workaround-eadr-windows-2003-32-bit-data-protector-7-03\/","url_meta":{"origin":1927,"position":4},"title":"Workaround: EADR Windows 2003 32 Bit &#8211; Data Protector 7.03","date":"4. M\u00e4rz 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":3016,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2016\/05\/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06\/","url_meta":{"origin":1927,"position":5},"title":"Prepare and execute EADR &#8211; Cell Server on Windows 2012 R2 and Data Protector 9.06","date":"13. Mai 2016","format":false,"excerpt":"{:en} In the past I often informed about the free EADR feature in Data Protector to recover clients and cell server. The last time I wrote an article in 2014 including two small scripts to get things prepared and automated - see https:\/\/www.data-protector.org\/wordpress\/2014\/04\/eadr-cell-server-dp-8-1x-windows-2012-r2\/. However, the batch files got broken due\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"EADR_23","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/EADR_23.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1927"}],"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=1927"}],"version-history":[{"count":10,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1927\/revisions"}],"predecessor-version":[{"id":2812,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/1927\/revisions\/2812"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=1927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=1927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=1927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}