01-21-2021 03:17 AM - edited 01-21-2021 03:22 AM
I am observing a behavior that needs illustration (Netbackup master server 8.2 windows based and media servers 8.2, and clients 8.1.2) .
I am facing that the master server can't connect on socket for some clients, but it was connected and the backup policy is configured, then when the backup policy runs, there are some child jobs finished successfully while other failed with network related erro (25, 24, 41,...), noting that the media server connects normally to the clients.
As far as I know, that the backup communication process is mainly between the master and the media and between media and client, and the master shouldn't communicate with the client during the backup process. But when I checked the parent job I found that there are streams return back with an error:
Operation Status: 24
Jan 21, 2021 3:08:09 AM - end Stream Discovery: Policy Execution Manager Preprocessed; elapsed time 0:38:17
Jan 21, 2021 3:08:09 AM - begin Stream Discovery: Stop On Error
Operation Status: 0
Jan 21, 2021 3:08:09 AM - end Stream Discovery: Stop On Error; elapsed time 0:00:00
Also I am observing that Policy Execution Manager preprocessing takes a long time before this error happened.
Is this due to the auto-discovery, where the master needs to connect to client? Noting that I am using full path selections neither wildcards nor ALL_LOCAL_DRIVES, but, I am writing the path not browsing it.
Any help to illustrate this behavior?
01-21-2021 06:26 AM
01-22-2021 11:45 AM - edited 01-22-2021 11:46 AM
No it is normal Linux and Unix filesystem backup (Standard policy)
01-22-2021 06:45 PM