HP does something weird

Not a big surprise when a big company roles out a product and it does something weird and all the current software that is supposed to work doesn't.

In this case it is HPs LTO 5 tape library, this the the FC connected version.
A large beast with 4 drives and 96 tape slots. Getting it all hooked up was quite straight forward, which was fortunate as there are no instructions at all anywhere.
Backup Exec sees it and you can load up the drivers etc. and all is well, you just can't do anything with the library as you can't open the doors to put tapes in or anything useful like use it.
The reason is our own fault as we have a CASO server and second backup server all hooked up through Fibre Channel to the libraries. 
Every other library we have had works fine with this set up and the MPIO software from Microsoft. But this new library won't. For some strange reason when you tell the library to Unlock it doesn't. Why, because we have two servers talking to it and it can't cope. Apparently when you right click and go unlock in Backup Exec, only the CASO tells the library to unlock, the other server doesn't so the lock stays, even if you go to the front panel you can't unlock it. What should happen is that both servers should send an unlock command.
The trick to fix this weirdness is a registry hack to disable the remote locking functionality on the server (PMR) then all is well.

This only affects environments with more than one server that connect to the library via a SAN.

Here's the link on the HP website that explains all.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3936307&prodTypeId=12169&prodSeriesId=3936307&objectID=c02191266

This may mean that I can finally get HP's Library and Tape Tools working, whenever I have tried running them before they just hang, maybe everything will now just work.

Or perhaps they wont.....

Comments

Post a Comment

Popular posts from this blog

Scripting DNS entries

For reasons to do with DR we needed to change our IP addressing scheme, either for our servers or for our PCs and printers and what not. Obviously changing PCs and printers was a whole lot easier due to the possible issues of inept developers’ hard coding IP addresses causing no end of problems with re-addressing the servers. This has entailed changing all the DNS entries for our printers, (whatever happened to the paperless office?) That in itself is no real challenge, they all have web interfaces so a quick connect and amend the setting then next printer. Updating the DNS entries was going to be a bit tiresome so I did a quick Google on how to do this with a script and up popped DNSCMD. You can run this from a CMD box on your PC, the main options you need to know are /recorddelete and /recordadd. To delete a record you simple need to type dnscmd <ServerName> /recorddelete <ZoneName> <NodeName> <RRType> <RRData>[/f] What does all that mean? Well i
Read more

Enterprise Vault - Failed Exchange Task

Here's another weird one. Enterprise Vault, we use this for e-mail archiving. It does a reasonable job. Probably no better or worse than any similar product. A couple of days ago I noticed that there was warning that it hadn't archived anything from one of our mailbox servers for a couple of days, not big issue as there is just a couple mailboxes on there as it used for testing at the moment. I had a look at the associated task and it was stopped. Started it and it failed. Error in the event log looked something like below The Task 'Exchange Mailbox Archiving Task for EXCH' failed to log on to Exchange server 'EXCH' using mailbox 'SMTP:EnterpriseVault@symantec.local'. Please ensure the mailbox has not been hidden, that the server is running and that the Vault account has sufficient permissions on the server. I went through every conceivable setting in AD, EV and Exchange trying to work out what had happened and why it wasn't working on thi
Read more

Windows Phone to iPhone - a painful transition

Windows Phone died a death due to a whole heap of incompetence from Microsoft.  My phone was an old Nokia 925, about 4 1/2 years old and bought and paid by my company. There were always low requirements for company phones, if it rung and you answered it, all was good. Then Hangouts reared its head (Google want to destroy MS, so WP support) but third-party support gave a stay of execution. The final nail was a requirement for out of hours support software that had no app for Windows Phone. I had to be “downgraded” to an iPhone 6s (yes, it is a low spec 2 version old iPhone, better hardware than my 925 but not really up there as a current version, how my company loves their staff, buy expensive crap rather than cheap crap). Stuff that just worked on my old phone, now needs 'me' to be re-engineered to work the Apple way.  This is only slightly less bad than the Google eat all your life and sell it back to you way, but it is like stepping back in to the 1990s Microsoft way
Read more