Backup to Data Domain fails with “Error: calling system(), returns nonzero. Err: 5040 Failed to connect to storage.”
| KB ID: | 2129 |
| Product: | Veeam Backup & Replication |
| Version: | 8.x, 9.x |
| Published: | 2016-05-02 |
| Last Modified: | 2020-08-13 |
Challenge
When preparing storage for backup you receive the following error message: "Error: calling system(), returns nonzero. Err: 5040 Failed to connect to storage"
Cause
The Data Domain chooses to use a different NIC than configured. Veeam is unable to communicate with the appliance as a result.
This is visible in the job logs:
Info Preparing storage '[REDACTED].vbk' for write. Is optimized for de-duplication media 'False'.
Info [AP] (9150) command: 'prepStorageForWriteEx\nddboost://[REDACTED].vbk\n8192\n0\n'
Info [AP] (9150) error: calling system(), returns nonzero. Err: 5040
This is visible in the job logs:
Info Preparing storage '[REDACTED].vbk' for write. Is optimized for de-duplication media 'False'.
Info [AP] (9150) command: 'prepStorageForWriteEx\nddboost://[REDACTED].vbk\n8192\n0\n'
Info [AP] (9150) error: calling system(), returns nonzero. Err: 5040
Solution
Re-add the repository to Veeam Backup and Replication with the production network IP address.
More information
EMC has documentation on this error message, though it does not pertain directly to Veeam; see below. For more in-depth assistance when troubleshooting this issue, it is recommended to contact EMC support.
https://community.emc.com/docs/DOC-26481
https://community.emc.com/docs/DOC-26481
| KB ID: | 2129 |
| Product: | Veeam Backup & Replication |
| Version: | 8.x, 9.x |
| Published: | 2016-05-02 |
| Last Modified: | 2020-08-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
