Failed to transfer file

[petzany]

I keep getting the error below when i try to copy files to the SFTP drive that’s connected can someone please help me with why this might be happening. Thank you

[2025/01/08 21:32:24.943] [ERROR ] [ 26500] [FILESYSTEM] FileSystem::MakeDir: [Z:explorer.exe] => AERROR::ALREADY_EXISTS : /archived
[2025/01/08 21:34:52.636] [ERROR ] [ 31536] [PROTOCOL ] _SFTP::SFTP::Upload filename: [VeeamAvailabilitySuite_9.5.Update4b.zip] , exec error: [42]
[2025/01/08 21:34:52.641] [ERROR ] [ 26500] [FILESYSTEM] FileOperation::WriteFile : AERROR::FILE_WRITE_FAILED
[2025/01/08 21:34:52.641] [ERROR ] [ 26500] [FILESYSTEM] FileSystem::Write => AERROR::FILE_WRITE_FAILED : archived/veem backup/veeamavailabilitysuite_9.5.update4b.zip, offset 2075131904, size 432958

[tsjeong]

Dear Petzany,

Thank you for reaching out. Based on the error logs you provided, here are some possible causes and solutions for the issue:

1. Directory Already Exists

• The log indicates that the directory /archived already exists on the SFTP server. This shouldn’t normally cause an issue, but it’s worth verifying the directory structure.

2. File Write Failure

• The error suggests a failure while writing the file veeamavailabilitysuite_9.5.update4b.zip to the SFTP drive. This could be due to one of the following reasons:
  • Insufficient permissions to write to the /archived/veem backup directory.
  • File size exceeding the limit set by the SFTP server.
  • Disk space on the SFTP server is insufficient.
  • Network interruptions during file transfer.

Suggested Steps:

• Verify the write permissions for the /archived/veem backup directory on the SFTP server.
• Check the available disk space on the SFTP server.
• Confirm that the file size does not exceed the server’s maximum file size limit.
• Ensure that the network connection is stable during file transfer.

If the issue persists, please provide a detailed log file so we can analyze further and assist you better.

To help us diagnose the issue:

1. Please set the log level to VERBOSE
2. Reproduce the problem.
3. Afterward, please follow the instructions in the following link to send us the debug log file:

How to attach a log file

1. Change Log Level First, check your settings and change log level to VERBOSE. 1A. If you cannot login At your login screen: [image] Click SETTINGS at the lower right corner. Change Log level to VERBOSE and go back to login screen to apply the change: [image] 1B. If you can login Go to Settings: [image] Change log level to VERBOSE: [22] Set to DEBUG if you use old version because there is no VERBOSE log level. Go back to DRIVES screen. Changed log level takes effect when you leave …

We greatly appreciate your patience and understanding. Once we receive the logs, we’ll work promptly to resolve your issue.

Best regards,
Bdrive Support Team