cancel
Showing results for 
Search instead for 
Did you mean: 

0xe00084ec HP Store once

Rajeev_theseeke
Level 3

started having this issue all of a sudden when backup to HP storeonce catalyst store started failing with error fomr one backup exec server (CAS) 

0xe00084ec 

lt writes some data and then finally fails; some vms data gets writeen.  Other member BE servers can write data backup to the same store once device on a diffrent catalyst store fine. 

I can see errors on the store once logs

"2022-10-13 05:49:21.230156 (local 18:49) : ERROR : 4520_20548 : 1571458 : +C : OST(MT) : oscpp::CommandSession::Close : Ln 233 : EXCEPTION: Close command session to AKHSO4K503 failed. : OSCLT_ERR_SERVER_OFFLINE [-1404] (from:oscpp::CommandSession::Close@233) 2022-10-13 05:50:46.037733 (local 18:50) : ERROR : 10800_14708 : 456 : TD : 15848 : AKHSO4K503 : Ix : OST(MT) : osCltTcp_Send : Ln 493 : Error sending on socket: 15848. Errno : 10060. 2022-10-13 05:50:46.037733 (local 18:50) : ERROR : 10800_14708 : 456 : TD : 15848 : AKHSO4K503 : Ix : OST(MT) : osCltTcp_Send : Ln 494 : GOTO ReturnStatus = -1 (Unknown).

"

 Support advised to lower the number of concurrent writes; already reduced to 10 from 16 

would  changing the stream size would help

Rajeev_theseeke_0-1665785417514.png

Can I remove and readd this storeonce device to backup exec server and reboot to see if that helps 

or can I add it to a member server and reconfigure job to use that member server; will I have to scan the whole store  

Very wiered issue driving me nuts 

Agan pretty new to Backup Exec 

 

3 REPLIES 3

Rajeev_theseeke
Level 3

had rebooted the be server multiple times after reducing the stream size

kf2013
Moderator
Moderator
   VIP   

hp storeonce 3540 error - Hewlett Packard Enterprise Community (hpe.com)

Seem the connection problem between the backup server and storeonce. What is the connection? (FC or LAN)?

Rajeev_theseeke
Level 3

this is now resolved; was a switch change; HP storeonce had etherchannel; we tested with disabling the swicth port that was replaced; and the backups starting runing successfully';  never ruleout network whatever the error