Configuring new devices and adding a new pool helped to solve this problem - looks like the error is not network-related but resources-related issue: with load being too high, the mgmt server is not capable to serve all the requests, especially when numerous multi-streams backup jobs are running, causing the sporadic "socket" errors. An interesting thing is that, the attempts to start the backup job may generate such error against different savesets in the backup job in arbitrary order.
Changing backup from "policy/workflow' to multi-stream "save' command initiated from client usually helps either to reduce such errors significantly or the backup job may proceeds w/o the 'socket' error at all, while switching over to a new pool helps to eliminate the errors.
I don't have enough statistics collected but week-long testing makes me feel that this is an efective solution for such problem. Thanks.
Such sporadic issues most often refer to a 'network related problem' where NW is only 'reporting' the problem because it will load the network if possible.
The problem itself could have a longer list of potential origins, related to either hardware and/or software. And because of connection problems, NW does obviously not have the chance to retrieve (better) status information to generate better error messages.
May I suggest that you contact Dell support to help in further tests/investigations.
vbduke
3 Posts
0
January 10th, 2022 06:00
Configuring new devices and adding a new pool helped to solve this problem - looks like the error is not network-related but resources-related issue: with load being too high, the mgmt server is not capable to serve all the requests, especially when numerous multi-streams backup jobs are running, causing the sporadic "socket" errors. An interesting thing is that, the attempts to start the backup job may generate such error against different savesets in the backup job in arbitrary order.
Changing backup from "policy/workflow' to multi-stream "save' command initiated from client usually helps either to reduce such errors significantly or the backup job may proceeds w/o the 'socket' error at all, while switching over to a new pool helps to eliminate the errors.
I don't have enough statistics collected but week-long testing makes me feel that this is an efective solution for such problem. Thanks.
bingo.1
2.4K Posts
0
December 29th, 2021 15:00
Such sporadic issues most often refer to a 'network related problem' where NW is only 'reporting' the problem because it will load the network if possible.
The problem itself could have a longer list of potential origins, related to either hardware and/or software. And because of connection problems, NW does obviously not have the chance to retrieve (better) status information to generate better error messages.
May I suggest that you contact Dell support to help in further tests/investigations.
vbduke
3 Posts
0
December 29th, 2021 15:00
Thanks! I have case opened with EMC for another reason - will ask them on this matter.