Skip to main content
  • EN

When running multiple backups at the same time backups fail with this error stack. How can I solve this?

 

RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 05/06/2025 22:46:41ORA-27191: sbtinfo2 returned errorAdditional information: 3475ORA-19511: non RMAN, but media manager or vendor specific failure, error text:   Broken pipe--tr:Cannot write data to the socket. Data size:  18636].--tr:Failed to write data into throttled device.--tr:Failed to asynchronously execute command  plugin.findRMANBackupFilesForSbtInfo] on backup server  xxx.xx.x.xx:10006].--tr:Cannot find RMAN bac

I would suggest contacting Support for this particular error as they will be better suited to assist you.

Hi ​@raymondvermeer -

Welcome to the Community! The Plugin really doesn’t do too awful much besides use a Veeam Repository.

https://helpcenter.veeam.com/docs/backup/plugins/rman_protection.html?ver=120

Are you using the Plugin as Standalone or Managed? On Windows or Linux? (assume Linux) Are your credentials to connect to a Veeam Repo ok? I saw a Forums post where a user had a somewhat similar issue & ended up installing a newer version of the Plugin and his error went away:
https://forums.veeam.com/veeam-backup-replication-f2/plugin-for-rman-error-ora-19511-failed-to-get-repository-by-id-t71315.html

Other than that...contacting Support as Chris suggests may be your best option:

https://helpcenter.veeam.com/docs/backup/plugins/veeam_rman_logs.html?ver=120’

Best

what is your repository, how is set repository and how many concurrent task do you have set?

issue  with plugin is, if you don’t have enough slots (concurrent tasks on repository), channels will be not in queue, but they will be aborted.

> Broken pipe--tr:Cannot write data to the socket. Data size: 18636].--tr:Failed to write data into throttled device.--

 

Very likely network issue (network drop, firewall, etc)

Strongly advise a support case as more details from the logs will be needed.

Comment


Terms & Conditions