“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.<\/p>\n
Normally the default behaviour of Windows is not a problem for Data Protector since the mechanism “Automatically detect changed SCSI addresses” will discover the new SCSI addresses using the serial number of the tape drive. However, in environments with several tape libraries attached to a server (i.e. when virtual tape libraries are used) the default Windows behaviour might mix the SCSI addresses between different library tape drives. The integrated mechanism in Data Protector will require in these cases some time to correct the problem with the changed SCSI addresses and will display some errors during the jobs. Using tape persistence the behaviour of Windows will be changed and in example a tape drive named “Tape0” becomes a symbolic name “Tape1236572535” (the symbolic name cannot be configured). With these new names error messages in Data Protector are prevented and the SCSI addresses or tape names stay unique.<\/p>\n
To enable tape persistence for Windows copy the code below, insert into text editor and save the content as .reg file. Execute the reg file and reboot the System. In addition RSM is disabled. Don’t forget to install the HP tape drivers, the installation routine can be downloaded within the corresponding HP Library. <\/p>\n
Update:<\/b> To use persistence fot the library robotic the additional key “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 default behaviour of Windows is […]<\/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":[175,174],"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-lH","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1927,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/04\/reviewed-persistent-binding-windows-2012\/","url_meta":{"origin":1345,"position":0},"title":"Reviewed: Persistent Binding Windows 2012","date":"1. April 2014","format":false,"excerpt":"{:en}In a previous article (see https:\/\/www.data-protector.org\/wordpress\/2013\/05\/persistent-binding-hp-lto-tape-drives-windows\/) I reported about \"tape persistence\" for Windows. In general there is noch change to adopt this for Windows 2012 and the registry keys are the same. However, a requirement is to activate \"Target Persistent Binding\" for the Fibre Channel HBA. In case of a\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":87,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/12\/was-ist-eigentlich-device-polling\/","url_meta":{"origin":1345,"position":1},"title":"What is device polling","date":"31. December 2010","format":false,"excerpt":"{:de}Bestimmt jeder Data Protector Kunde mit einer Fibre Channel Tape Library hat dieses Problem schon mal wissentlich oder unwissentlich erlebt: ein SCSI Reset w\u00e4hrend einer Sicherung... und das ganze Band ist zerst\u00f6rt. Was war passiert? Das Bandlaufwerk wurde mit\u00a0SCSI Kommandos \u00fcbersch\u00fcttet - das nennt man auch Device Polling. Polling ist\u2026","rel":"","context":"In "Common"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":100,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/12\/disable-device-polling\/","url_meta":{"origin":1345,"position":2},"title":"Disable Device Polling","date":"31. December 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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2190,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/eadr-tape-block-size\/","url_meta":{"origin":1345,"position":3},"title":"EADR and Tape Block Size","date":"1. January 2015","format":false,"excerpt":"{:en}In older articles I often wrote about Bare Metal Recovery, a feature included in Data Protector without any additional costs and called Enhanced Automated Disaster Recovery (EADR) - see https:\/\/www.data-protector.org\/wordpress\/?s=eadr. To recover the Cell Server (see link) I always told to use tape devices with a block size of 64K.\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2414,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/11\/hewlett-packard-enterprise-libraries-lto-7-arrived\/","url_meta":{"origin":1345,"position":4},"title":"Hewlett Packard Enterprise Libraries – LTO-7 arrived","date":"30. November 2015","format":false,"excerpt":"{:de} In einem fr\u00fcheren Artikel hatte ich \u00fcber die Zukunft von Bandtechnologien informiert - siehe https:\/\/www.data-protector.org\/wordpress\/2015\/09\/future-tape-technology\/. P\u00fcnktlich zur Discover stellt Hewlett Packard Enterprise die neuen LTO-7 Laufwerke in ihren Produkten vor, in zwei frischen Videos (auf YouTube). {:}{:en} In a previouse article I informed about the future of tape technology\u2026","rel":"","context":"In "Data Protector Links"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1478,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/07\/write-device-parameter-incorrect\/","url_meta":{"origin":1345,"position":5},"title":"Cannot write to device – the parameter is incorrect","date":"5. July 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 "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1345"}],"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=1345"}],"version-history":[{"count":8,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1345\/revisions"}],"predecessor-version":[{"id":2659,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1345\/revisions\/2659"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1345"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1345"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1345"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\MChgr\\Persistence=00000001<\/code> is required. In this example the device Changer1:0:0:0 becomes the symbolic name Changer2147483646:0:0:0. With this feature enabled the robotic stays unique as it is the case with tape drives during reboots.<\/p>\n\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[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NtmsSvc]\r\n\"Start\"=dword:00000004\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"