Yes, I understand that the 134 error code is not a normal error. We've got this error because our backup windows is very full off...
Backup process is launching by Control M, and we allow multistream for backup.
1 stream for the federal site, 1 stream for the replicated site, and 1 parent process. But this three process have been launch at the same time.
In the activity monitor when the backup is running, we could see differences on the avancement of the backup : let's me explain.
The first one is allready backing up files without finish the count of files to backup
The second one is counting the number of files to backup without starting to backup files
And the parent job is waiting, no count of files, no files backup.