[Veritas-bu] SAN client config question

2009-01-09 Thread bruceephx
I am working on upgrading 6.0 MP5 to 6.5.3 in a Windows only environment. For the purposes of using SAN client and Fibre Transport, can I have the Master/Media on Windows and the client on Windows? It appears that the target has to run on Linux or Unix. So can a Windows Server be the target

Re: [Veritas-bu] NBU 6.5.1 nbsl error

2009-01-09 Thread Christopher Robin Zimmerman
NBU 6.5.1 on Solaris 9 media server - nbsl error when starting NetBackup: ld.so.1: nbsl: fatal: relocation error: file /opt/openv/netbackup/bin/nbsl: symbol __1cDstdTbasic_istringstream4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___G_ _vtbl_: referenced symbol not found All other processes/daemons

Re: [Veritas-bu] SAN client config question

2009-01-09 Thread Spellacy, Sean
Talked to my rep about this the other day and the answer is currently no, only redhat and solaris currently supported He did mention something about future releases 6.5.4 or 6.5.5 but don't quote me on that. The current HBAs supported can be found here

[Veritas-bu] SAN client config question

2009-01-09 Thread bruceephx
Thanks Sean, thats what I figured based on my readings. Sucks that Windows is stuck with LAN transports. We have HP EVA storage arrays with higher levels of integration to HP SAN software for managing the storage. We can do EVA snapshots from Windows. But we still can't do backups from

[Veritas-bu] Socket Error 23 - Backup failed.

2009-01-09 Thread nitin.gizare
HI one of the policy has exited with Socket error 23 code, Some recommendations to check on the name resolution between serve and client which seems to be fine. I am interested to find required patches which needs to be installed in client ., Our client is solaris 2.8 . Pls help me to get