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