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

[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 required information.



Rgds

Nitin


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] SAN client config question

[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 storage assigned to 
one Windows server to another Windows server without getting the LAN involved.  
I would do snapshots but all the EVA space is for primary storage.  Our backup 
storage is on MSA's and HP says we can't do snapshots to MSAs from EVAs.

We are good on the HBAs, using OEM'ed QLogic cards from HP.

I will keep my fingers crossed about the future versions.  As they say on my 
satellite TV forum about getting new HD, it's coming 'soon'.

+--
|This was sent by bruce.ellefr...@phoenix.gov via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] SAN client config question

[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
ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Serv
er/284599.pdf

Regards
SSS

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
bruceephx
Sent: Friday, January 09, 2009 8:17 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] SAN client config question


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 for the SAN client?

Thanks in advance.

+--
|This was sent by bruce.ellefr...@phoenix.gov via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NBU 6.5.1 nbsl error

[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 startup fine and backups are working.
>
>Any ideas?

This could mean something that SHOULD be at the 6.5.1 level is still at
the 6.5 level and you're seeing the result of a binary mismatch between
nbsl and one of the libraries it's depending upon.

Was this server recently upgraded?

Would it be possible to reapply the 6.5.1 release updates?  (I'd try the
CLT update first.)

Thanks,
CRZ

--
Christopher Robin Zimmerman - 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] SAN client config question

[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 for the SAN 
client?

Thanks in advance.

+--
|This was sent by bruce.ellefr...@phoenix.gov via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] NBU 6.5.1 nbsl error

[Marianne Van Den Berg]

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 startup fine and backups are working.

 

Any ideas?

 

 

 

Kind Regards

 

Marianne 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu