Hi
There are at least two techniques that provide persistent naming for tape
devices in Windows environments. Here are two that I've tested with NetWorker,
and know that they work.
1. Microsoft Windows
[Microsoft Knowledgebase article 873337]
Windows 2003 SP1 and later provide persistent names for tape devices. If the
following Registry entry is created:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Tape\Persistence [DWORD
value of 1]
and the system is rebooted, device file \\.\Tape0 becomes something like
\\.\Tape2147483646, which is persistent. Note, however, that this feature may
not work correctly for IBM tape devices if the IBM Tape Driver is also
installed.
2. IBM Tape Driver
The 'IBM Tape Device Drivers Installation and User's Guide' describes
persistent naming support. This support began in v6.1.6.2 of the IBM Tape
Driver. To use this feature:
* Install the driver
* Add a value in the registry called PersistentNaming and assign it a
value 1 at:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k3
* reboot
This provides device files of the form \\.\Tape4801105 that do persist when
other devices are added or removed. NetWorker V7.5 can use these devices
(NetWorker bug LGTsc17131 addressed and fixed an earlier problem that prevented
use of these persistently-named device special files).
tl
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Matthew Huff
Sent: Friday, December 11, 2009 4:58 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Creating fake \\.\TapeX devices in Wintel
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Tape
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type Persistence, and then press ENTER.
5. Right-click the Persistence registry entry, and then click Modify.
6. Type 1 in the Value data box, and then click OK.
7. Quit Registry Editor.
8. Restart the computer.
The Window's plug and play driver will be disabled for tape devices. The names
will be like \\.\TapeXXXXX where XXXXX is the serial id of the drive. JBCOnfig
the drives and assign the right tape drive to the right order (use inquire,
etc...) and then disable the broken drives.
----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
http://www.ox.com ; | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Reed, Ted G [IT]
Sent: Friday, December 11, 2009 4:46 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Creating fake \\.\TapeX devices in Wintel
I have a Windows 2000 server instance providing Networker 7.2.1 master service,
attached to a Dell136T with LTO1 drives. However, the last powercycle of the
Dell came up with only 2 of the 4 drives online. The other 2 report hard
errors on the library console/LCD. Thing is, I can survive just fine on two
drives....the environment has been shrinking. But the Wintel + Dell reboot
also re-ordered the drives, so I can't simply down the 2 broken and leave the
other 2 online...I have to rebuild the jukebox.
This is where my problem comes in. JBCONFIG of autodetected SCSI of the 136T
tries to force me to enter values for elements 254, 255, 256, and 257. And
only 256/257 are working devices. No matter what I try, jbconfig will only
accept \\.\Tape0 and \\.\Tape1 (discovered)...and I can't repeat them then
disable either. But what about the other 2 elements? Can I create a spoof or
fake \\.\Tape2 and \\.\Tape3 so that I can put the broken drive elements as the
spoofed values, and the working drive elements with their proper discovered
device path?
Any other ideas are welcome....I had not anticipated being forced to enter 4
different \\.\TapeX values when I only have 2 recognized by the OS. Thanks.
--Ted
This e-mail may contain Sprint Nextel Company proprietary information intended
for the sole use of the recipient(s). Any use by others is prohibited. If you
are not the intended recipient, please contact the sender and delete all copies
of the message.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
