NetWorker: Il backup del database Sybase viene avviato ma non viene eseguito correttamente durante la fase di completamento

Il backup del database Sybase viene avviato ma non viene eseguito correttamente durante la fase di completamento.
Errore:

D00: ERRORE SYBMULTBUF: Comunicazione tra processi dell'emulatore non riuscita con stato di errore = 9, codice errore =0, system message=Pipe I/O restituito 0 byte.
Errore di apertura del server: 16248.10.0: Errore in srv_select(), il descrittore di file 12 non è più attivo.
 

Backup Server: 4.194.2.1: Internal error. The srv_select() function was called to complete an I/O for 2240 bytes. After retrying 2241 times only 0 bytes have been read.
Backup Server: 4.141.2.75: [0] The 'read' call failed for database/archive device while working on stripe device 'nsrsyb::..4.1./nsr/apps/tmp/sybtmp_1014766.txt::000' with error number 0 (Success). Refer to your operating system documentation for further details.
Backup Server Internal Error: 4.62.3.1: Multibuffering subprocesses died, archive nsrsyb..4.1./nsr/apps/tmp/sybtmp_1014766.txt::000.
Backup Server: 4.141.2.66: [0] The 'write' call failed for database/archive device while working on stripe device 'nsrsyb::..4.1./nsr/apps/tmp/sybtmp_1014766.txt::000' with error number 32 (Broken pipe). Refer to your operating system documentation for further details.
Backup Server Internal Error: 4.62.3.8: Multibuffering subprocesses died, archive nsrsyb:..4.1./nsr/apps/tmp/sybtmp_1014766.txt::000.

sybmultbuf si arresta in modo anomalo
Stack di sybmultbuf:

Backup Server: 4.188.1.1: Database : 267710850 kilobytes (89%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database : 268552362 kilobytes (100%) DUMPED.
A00: SYBMULTBUF: bs_trap; process received signal 11
A00: 0x7f6a508bcad0 : (killpg+0x40) [0x7f6a508bcad0]
A00: 0x7f6a50c3da74 : (__pthread_mutex_lock+0x4) [0x7f6a50c3da74]
A00: 0x7f6a5038d352 : (lg_atomic_decrement+0x22) [0x7f6a5038d352]
A00: 0x7f6a50289dc0 : (nw_ddcl_disconnect+0xa0) [0x7f6a50289dc0]
A00: 0x7f6a501e2302 : (xdup_ddinfo_ext+0x1a2) [0x7f6a501e2302]
A00: 0x7f6a501e257e : (dd_wrapper_fini+0x8e) [0x7f6a501e257e]
A00: 0x7f6a501e26b3 : (dd_cleanup+0x23) [0x7f6a501e26b3]
A00: 0x7f6a503a5210 : (lg_atexit_execute_and_remove_all+0x70) [0x7f6a503a5210]
A00: 0x7f6a50144a8e : (syb_close+0x12e) [0x7f6a50144a8e]
A00: 0x44da4f : (api_close+0x20f) [0x44da4f]
A00: 0x4293a2 : (ctl_job+0x39c) [0x4293a2]
A00: 0x425fe8 : (archive_proc+0x593) [0x425fe8]
A00: 0x42526a : (sybmbuf_main+0x66e) [0x42526a]
A00: 0x424bfa : (main+0x1b) [0x424bfa]
A00: 0x7f6a508a8ca3 : (__libc_start_main+0xf3) [0x7f6a508a8ca3]
A00: 0x424b09 : (_start+0x29) [0x424b09]

Si tratta di un difetto di codice che influisce su tutti i processi o client che comunicano direttamente con libDDBoost/DDR.

Il problema è stato risolto in NetWorker 19.7.0.4 e NetWorker 19.8.0.1 e versioni successive.

Ambiente: 
Red Hat 8.6
NetWorker/NMDA 19.7.0.1
NetWorker viene implementato in un ambiente AWS.