Device names

Hi Jason,

Is persistent binding turned on for the drive?  This makes sure that if you reboot the system, drives do not get reordered.  If this happens, NetWorker will get   I believe the technical upgrade note has a section that describes how to set it.

Thanks,

Allan

After much searching and digging around on PowerLink, I've found where to set persistent binding on Windows Server 2003 R2.  It is a registry edit, however, it is already enabled.  I decided to try a chat session with EMC support and both times it went nowhere.  The first session was disconnected prematurely and the tech from the second session said I should open a ticket because this issue will need to use webex.  Which they can't do through the chat program. 

I still don't get why this drive isn't using persistent binding but my other two VTLs are using persistent binding.  I also found a registry key where I could change the name of the Autoloader but after rebooting the server the name was changed back.  So, what is overriding the registry value?  This is a good one eh?

I think you might have just hopped over into a support issue.  I'd open up that ticket and get them involved.  Maybe the library firmware is not returning a value the OS or NetWorker is expecting.

As far as your dre name- I was also going to post some lyrics or a video from that album you had memorized... But after looking at them, don't think that would be wise. 

Hi,

Persistant naming and persistant binding are two different things.

When you say persistant binding, it's SAN related stuff, what target connect to which initiator. (Drifve/controller <--> Host )

Persistant naming is related to windows internal "plug & play" naming your target to ex \\.\Tape0 (w.o. persist naming) or \\.\Tape2123455

Persistant naming is done on driver level or global(instance) so it might be that you use different HBA:s for the two

VTLs or do they use different drivers maybe?!

There is good info in docs: Technical GUidance for Upgrades to EMC Networker 7.4sp2 and

                                       Configure Tape Devices for EMC NetWorker.

But I assume that you already have them, as you searched powerlink.

Good luck with the registry hacking,

regards

Håkan

Hello

i am about a Newbie in Networker Support althaught i ve been using the champ for about 2 years but i am still walking my 1st steps ; however i have a feeling that this issue is purely related to OS<->hardware interaction

i would recommend checking the drivers version against the new library and trying to kick a few CLI stuff ; changers , inquire , sjirdtag ,...... and see if the answers of those guys look consistent

Happy troubleshooting

Shareef

Shareef,

I would agree with you that this seems to be an OS - hardware issue.  Unfortunately I'm not familiar with CLI commands so I need to just contact tech support about this.  Although I hate doing that, it is like admitting defeat!  haha

Hakan,

Thanks for the reply, after reading your post I would say that my issue has to due with persistent naming and not persistent binding.  Do you know if persistent naming has to be enabled for each device?  Or is it something that would enabled at the OS level?  The reason I ask is that both of my VTLs are using persistent naming already. 

Jason,

i understand your concern ; in fact CLI stuff are quite painfull , especially with different output from different OSs

as a last point ; could you uninstall and re-install the driver ? did you re-install a new driver after replacing the old faulty library ?

if this does not change the status ; lets wait for the feedback from the support guys

cheers

Hm..

I think that the per driver, but the built in from Microsoft is using the what I call the "generic" entry in the registry.

Check:  HKLM\System\CurrentControlSet\Control\Tape\Persistence:DWORD=1

1= Persistant naming on ; 0=Persistant naming off.

( more info on: http://support.microsoft.com/kb/873337/en-us)

But if you use drivers from example IBM, you set the registry entry there.

If you check inte Win device manager, have all the drives attached to the same driver ?

One tricky thing when working w VTL:s. Did you create another logical robot and presented it to the host or

is it a new hardware ? (Then you present "new" hardware from the same originating SAN port, and I do belive that

the binding is done on the target port information in windows.)

Just a wild sequense that I would test atleast.

Turn persistant naming off and reboot the server. (Verify that you get new targets in windows.)

(maybe even pull that SAN cables so all tape drives are gone + reboot)

Turn persistant naming on again, reboot. (Check that you get persistant names turn up. match VTL drives w Win drivers.

IF ok, go into NetWorker, change your robots. (rescan devices, enable your robots again, create a new one if needed.)

Yes, it can be a frustrating to change hw on a server.

regards

Håkan

Hakan,

I have tried turning persistent naming on and off in the registry key that you provided.  It does not seem to be working for the physical tape device.  However, I did notice that when I turned the persistent naming off the names for the VTLs all changed and they changed again when I re-enabled persistent naming.  So, it seems to be working on my VTL but not on my physical tape device. 

After talking with EMC tech support, the tech decided that this was ok and should not affect the performance.  She really didn't seem all that interested in figuring out why the physical tape device used to be called \\.\Tape21478363 and now it is \\.\Tape0.  So, I guess I'm stuck with that name. 

However, she was not able to figure out why I am not able to label new or old tapes, either virtual or physical.  I just created a new ticket with EMC support and will see what they have to say about it.  I just wanted to say thanks to everyone for their time and effort and will keep you posted on what I come up with for my new problem.  Good times!