Solaris?

You need to use sg driver for robot device name.

Does sgscan or scan see the sg device name for the robot?

If not, please have a look at this post:

https://www-secure.symantec.com/connect/forums/solaris-111-sas-lto6-neo-400s-library-can-not-bring-netbackup

Hi Marianne,

Thanks for your help, you know i was looking in the release notes for 7.5.0.5 and i found this hotfix

So i think if i rebuild the SG driver its supposed to work well, i will check the link and give the feedback

Thansk for the help

Alejandro

Hi Marianne,

I have bad news, even with the support from SYMANTEC i didnt solve the issue and because problems of time in the implementation i used WINDOWS SERVER and the library is working well. In my labs I wil install the latest version of Solaris and try again installing the latest version of Netbackup so i can test more if it will work.

As Always thank you for your help.

Hope to see you soon in the forums

Alejandro

I still feel that this is a Solaris/Oracle issue, not NetBackup.

yes, it showuld be, i will do some test later, thanslk for your help

Alejandro

Agree with marianne.  That looks like an OS issue to me.

It really is very very rare for NBU to be 'involved' with device issues.  

Martin

the main problem is that NBU needs 2 drivers to run the library if i dont get wrong is de ST and SG driver, SAS2 interfaces under Solaris can only manage just one driver thats the way it doesnt work. But with the latest hotfix in NBU 7.5.0.5 NBU added the compatibility with this library as I show up in this post. But after the installation and everything it doesnt work.

As per my post over here, the problem is with the driver of the 6 GB HBA which SUN/Oracle need to fix.

The problem is not with NBU.

Do you have a call open with Oracle? 

Seems the only workaround is to use a 3 GB HBA in the meantime.

For now the only workaround is the 3 gb HBA as Marianne saids, i also opened a case with oracle, the answer was to update the drivers for the HBA but the main solutios is the 3GB HBA for now, i think also it would be interesting to give it a try installing the new version of solaris 01/13 maybe there is a solution for this issue